This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: No SOAP libraries available for Python 3.x
Type: Stage: resolved
Components: Library (Lib) Versions: Python 3.2
process
Status: closed Resolution: rejected
Dependencies: Superseder:
Assigned To: Nosy List: Michiel.Van.den.Berghe, brian.curtin
Priority: normal Keywords:

Created on 2011-04-19 15:17 by Michiel.Van.den.Berghe, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (2)
msg134064 - (view) Author: Michiel Van den Berghe (Michiel.Van.den.Berghe) Date: 2011-04-19 15:17
There doesn't seem to exist a SOAP library for Python 3.x. Several different third party libraries exist for the 2.x releases, but none of these are being ported to 3.x. None of these modules are easily ported using 2to3 due to string encoding issues.

Seeing how SOAP is a major webservices technologies, I think Python should get its own standard SOAP module to keep up with its "batteries included" principle.
msg134065 - (view) Author: Brian Curtin (brian.curtin) * (Python committer) Date: 2011-04-19 15:23
This is something that should be handled on the trackers of any of the external SOAP libraries. If they are ported to Python 3 and are seen as best in class and are willing to move all development into the standard library, then inclusion could be considered.

It's unlikely that all of that will come together in time for the 3.3 release, as the library needs to be proven in the wild after being ported.

If someone does come up with a popular 3.x SOAP library, an email to python-dev or python-ideas would be enough to kick off an inclusion discussion.
History
Date User Action Args
2022-04-11 14:57:16adminsetgithub: 56087
2011-04-19 15:23:26brian.curtinsetstatus: open -> closed

nosy: + brian.curtin
messages: + msg134065

resolution: rejected
stage: resolved
2011-04-19 15:17:29Michiel.Van.den.Berghecreate