Suds

- 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 namespacing.
- WSDL part types no longer default to WSDL `targetNamespace`.
- Fixed Tickets: 4, 6, 21, 32, 62, 66, 71, 72, 114,
155, 201.

- 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.

- 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.

- 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.

- 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()`.

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