All,
Suds version 0.3.1 has been released. See https://fedorahosted.org/suds/ for details.
If you never upgraded to 0.3, you can disregard the description below.
In short, this is a quick follow up to the 0.3 release that enhanced suds support for multi-port services but also made the burden on the user more then necessary. After more consideration (and a good night sleep), it seemed obvious that a few changes would mitigate the impact on users: 1) filter out the non-soap bindings - they were causing the real trouble in 0.2.9 and earlier; 2) be smarter about how suds selects the port. Since most servers are happy with any of the soap (1.1 and 1.2) bindings, ambigious references to methods when invoking them without the port qualification will work just fine in almost every case. I don't want to make the user do anything when it's not necessary. Suds is supposed to be simple & easy :).
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 if they upgraded to 0.3.
So, if you've because of the upgrade to 0.3 you've updated your code to:
client.setport()
-or-
client.merge_methods() <--- remove this for sure, it no longer exists.
-or (port-qualified invocations) -
client.service.<port>.<method>
you can probably revert these changes after upgrading to 0.3.1. In some cases, however, you may really need to specify the port. This will be obvious if after upgrading to 0.3.1 and reverting your code to the way it was when working with 0.2.9 and earlier, you are getting MethodNotFound exceptions or WebFaults from your server.
Sorry for any inconvenience!
Regards,
Jeff