Be the first to post a text review of suds. Rate and review a project by clicking thumbs up or thumbs down in the right column.

View all reviews

• suds 0.3.4 file released: suds-0.3.4-py2.5.egg

  posted 392 days ago

• suds 0.3.4 file released: suds-0.3.4.tar.gz

  posted 392 days ago

• File released: /suds/0.3.4/suds-0.3.4-py2.5.egg

  posted 392 days ago

• File released: /suds/0.3.4/suds-0.3.4.tar.gz

  posted 392 days ago

• suds 0.3.1 file released: python-suds-0.3.1-1.noarch.rpm

  version 0.3 (9-30-08): * 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 Docuemnt/Literal:' * Add support for (xs:group, xs:attributeGroup) tags. * Add Client.last_sent() and Client.last_received(). version 0.3.1 (10-1-08): * 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.

  posted 463 days ago

• File released: /suds/0.3.1/python-suds-0.3.1-1.noarch.rpm

  posted 463 days ago

• suds 0.3.1 file released: suds-0.3.1.tar.gz

  version 0.3 (9-30-08): * 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 Docuemnt/Literal:' * Add support for (xs:group, xs:attributeGroup) tags. * Add Client.last_sent() and Client.last_received(). version 0.3.1 (10-1-08): * 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.

  posted 463 days ago

• suds 0.3.1 file released: suds-0.3.1-py2.5.egg

  version 0.3 (9-30-08): * 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 Docuemnt/Literal:' * Add support for (xs:group, xs:attributeGroup) tags. * Add Client.last_sent() and Client.last_received(). version 0.3.1 (10-1-08): * 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.

  posted 463 days ago

• File released: /suds/0.3.1/suds-0.3.1-py2.5.egg

  posted 463 days ago

• File released: /suds/0.3.1/suds-0.3.1.tar.gz

  posted 463 days ago