Suds

Latest version: v1.1.2

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

Scan your dependencies

Page 5 of 8

0.3.3

- No longer installs (tests) package.
- Implements API-3 proposal
(<https://fedorahosted.org/suds/wiki/Api3Proposal>).
- Pluggable transport.
- Keyword method arguments.
- Basic 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), ambiguous 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 us not make the user do it when it is not necessary. In most
cases, users on 0.2.9 and earlier will not have to update their
code when moving to 0.3.1 as they might have in 0.3.

0.3

- Extends the support for multi-port services introduced in 0.2.9.
This addition, provides for multiple services to define the *same*
method and `suds` will handle it properly. See section \'SERVICES
WITH MULTIPLE PORTS:\'.
- Add support for multi-document document/literal SOAP binding style.
See section \'MULTI-DOCUMENT Document/Literal:\'.
- Add support for `xs:group`, `xs:attributeGroup` tags.
- Add `Client.last_sent()` and `Client.last_received()`.

0.2.9

- Support for multiple ports within a service.
- Attribute references `<xs:attribute ref=""/>`.
- Make XML special character encoder in sax package - pluggable.

0.2.8

- Update document/literal binding to always send the document root
referenced by the `<part/>`. After yet another review of the space
and user input, seems like the referenced element is ALWAYS the
document root.
- Add support for \'binding\' `schemaLocation`s to namespace-uri. This
is for imports that do not specify a `schemaLocation` and still
expect the schema to be downloaded. E.g. Axis references
\'<http://schemas.xmlsoap.org/soap/encoding/>\' without a
schemaLocation. So, by doing this:

>
> from suds.xsd.sxbasic import Import
> Import.bind('http://schemas.xmlsoap.org/soap/encoding/')
>

The schema is bound to a `schemaLocation` and it is downloaded.

- Basic unmarshaller does not need a [schema]{.title-ref}. Should have
been removed during refactoring but was missed.
- Update client to pass kwargs to `send()` and add `location` kwarg
for overriding the service location in the WSDL.
- Update marshaller to NOT emit XML for object attributes that
represent elements and/or attributes that are *both* optional and
`value=None`.
- Update factory (builder) to include all attributes.
- Add `optional()` method to `SchemaObject`.
- Update WSDL to override namespace in operation if specified.
- Fix schema loading issue - build all schemas before processing
imports.
- Update packaging in preparation of submission to fedora.

Page 5 of 8

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.