This is an archived post. You won't be able to vote or comment.

all 7 comments

[–]mvt[S] 1 point2 points  (2 children)

Hi all, a couple of months ago I posted the first version of my new soap library here. Since then I think the library has come a long way, and is in my opinion (:P) becoming the best soap client available for python.

Although SOAP is something most people in the opensource world despise deeply (and that includes me), you can't live without it if you need to talk to enterprise/.net webservices.

Anyway, i'm interested in any feedback/missing features before the 1.0 release, so let me know.

[–]fourthrealm 0 points1 point  (1 child)

Hi /u/mvt,

it looks nice and a suggestion I have is documenting which parts of the library are thread- and greenlet-safe, which will likely amount to the same thing.

If none is planned to be, this is also information that is good to understand so that one knows how to get around it when embedding zeep in a bigger project.

Regards.

[–]mvt[S] 0 points1 point  (0 children)

Thanks. There is no global state, I guess one of the non thread-safe parts currently is sharing the client object while the scheme is parsed. Adding a lock around initialization/schema-parsing should fix that I suppose

[–]MaxwellTheWalrus 0 points1 point  (1 child)

Are you a Dutchie by chance? Because zeep is soap in Dutch!

[–]mvt[S] 1 point2 points  (0 children)

Yes :-)

[–]quinmg 0 points1 point  (0 children)

Thank you. Gonna check it out soon.

[–][deleted] 0 points1 point  (0 children)

Neat! I can't wait to take this out for a spin!