Suds-ews

Latest version: v0.3.7

Safety actively analyzes 613649 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 3

0.3.6

* Change hard coded /tmp/suds to tempfile.gettempdir() and create suds/ on demand.
* Fix return type for Any.get_attribute().
* Update http caching to ignore file:// urls.
* Better logging of messages when only the reply is injected.
* Fix XInteger and XFloat types to translate returned arrays properly.
* Fix xs:import schema with same namespace.
* Update parser to not load external references and add Import.bind() for XMLSchema.xsd location.
* Add schema doctor - used to patch XSDs at runtime. (See Option.doctor)
* Fix deprecation warnings in python 2.6.
* Add behavior for default defined on <element/>.
* Change xsi:type value to always be qualified for doc/literal. (reverts 0.3.5 change).
* Add Option.xstq option to control when xsi:type is qualified.
* Fixed Tickets: 64, 129, 205, 206, 217, 221, 222, 224, 225, 228, 229, 230

0.3.5

* Adds http caching. Default is (1) day. Does not apply to method invocation. See: documentation for details.
* Removed checking fedora version check in spec since no longer building < fc9.
* Updated makefile to roll tarball with tar.sh.
* Moved bare/wrapped determination to wsdl for document/literal.
* Refactored Transport into a package (provides better logging of http headers).
* Fixed Tickets: 207, 209, 210, 212, 214, 215

0.3.4

* Static (automatic) Import.bind('http://schemas.xmlsoap.org/soap/encoding/'),
users no longer need to do this.
* Basic ws-security with {{{UsernameToken}}} and clear-text password only.
* Add support for ''sparse'' soap headers via passing dictionary
* Add support for arbitrary user defined soap headers
* Fixes service operations with multiple soap header entries.
* Schema loading and dereferencing algorithm enhancements.
* Nested soap multirefs fixed.
* Better (true) support for elementFormDefault="unqualified" provides more
accurate namespaing.
* WSDL part types no longer default to WSDL targetNamespace.
* Fixed Tickets: 4, 6, 21, 32, 62, 66, 71, 72, 114, 155, 201.

0.3.3

* No longer installs (tests) package.
* Implements API-3 proposal ( https://fedorahosted.org/suds/wiki/Api3Proposal )
- Pluggable transport
- Keyword method arguments
- Baisc http authentication in default transport
* Add namespace prefix normalization in soap message.
* Better soap message pruning of empty nodes.
* Fixed Tickets: 51 - 60

0.3.2

* SOAP {{{MultiRef}}} support ''(1st pass added r300)''
* Add support for new schema tags:
* <xs:include/>
* <xs:simpleContent/>
* <xs:group/>
* <xs:attributeGroup/>
* Added support for new xs <--> python type conversions:
* xs:int
* xs:long
* xs:float
* xs:double
* Revise marshaller and binding to further sharpen the namespacing of nodes produced.
* Infinite recursion fixed in ''xsd'' package dereference() during schema loading.
* Add support for <wsdl:import/> of schema files into the wsdl root <definitions/>.
* Fix double encoding of (&)
* Add Client API:
* setheaders() - same as keyword but works for all invocations.
* addprefix() - mapping of namespace prefixes.
* setlocation() - Override the location in the wsdl; same as keyword except for all calls.
* setproxy() - same as proxy keyword but for all invocations.
* Add proper namespace prefix for soap headers.
* Fixed Tickets: 5, 12, 34, 37, 40, 44, 45, 46, 48, 49, 50, 51

0.3.1

* Quick follow up to the 0.3 release that made working multi-port service definitions
harder then necessary. After consideration (and a good night sleep),
it seemed obvious that a few changes would make this much easier: 1) filter out
the non-soap bindings - they were causing the real trouble; 2) since most servers
are happy with any of the soap bindings (soap 1.1 and 1.2), ambigious references to methods
when invoking then without the port qualification will work just fine in almost every
case. So, why not just allow suds to select the port. Let's not make the user do it
when it's not necessary. In most cases, uses on 0.2.9 and earlier will not have to
update there code when moving to 0.3.1 as they might have in 0.3.

Page 1 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.