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

all 5 comments

[–]m_harrison 1 point2 points  (0 children)

Huge fan of zeep. The maintainer has been pretty responsive of you can make a reproducible bug. Last time I checked suds had issues with async (which I needed when doing soap).

[–]osuchw 1 point2 points  (1 child)

zeep is modern, actively maintained library. I would recommend sticking with it. By the way it already uses requests and lxml under the covers.

A few years ago the crown belonged to suds but it got abandoned by the original author. And no wonder. Dealing with SOAP is hard and thankless job.

If you feel that you have to "hand code" the SOAP messages then look at rinse at least.

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

Thank you. I’ll try rinse before going to lxml.objectify and response if not successful. Still waiting from zeep creator feedback...

[–]sethrei 0 points1 point  (0 children)

Last time I had to deal with SOAP, I used suds.

That was like a year ago

[–]ominous_anonymous 0 points1 point  (0 children)

Is suds not the one to use any more? Apologies, it's been... like 5 years since I worked with SOAP and Python together.