Open GoogleCodeExporter opened 9 years ago
can you provide a patch or diff?
also, testcases would be useful
Original comment by reingart@gmail.com
on 14 Jan 2013 at 6:43
I've included a patch for client.py.
I'm not sure how best to produce a useful testcase for this since the issue
happens during the client call request, making the erroneous (or correct)
output only visible either in the trace output or from the server result.
I have, however, included a small script that, while not useful as a unit test,
can be used to visually verify an xml object against it's traced output during
a soap request. The 'a="b"' attribute/value on the "test" request tag will be
visible in the first printout, but not the second (trace) output without the
included patch. After the patch, both sets of output should be identical (minus
the xmlsn attribute that is also added).
Original comment by secreti...@gmail.com
on 18 Jan 2013 at 9:14
Attachments:
Hi,
I stumbled uppon the same issue and worked arround it a different way (passing
an "attributes" param to call()) but I find secretions approach much more
logical.
Original comment by joce...@crapouillou.net
on 30 Sep 2013 at 8:15
Bump.
Any update ?
Original comment by joce...@crapouillou.net
on 27 Nov 2013 at 2:04
Sorry for the delays.
If you can, please make a pull request on github (that will be faster and
easier to merge the patch):
https://github.com/pysimplesoap/pysimplesoap
Original comment by reingart@gmail.com
on 20 Dec 2013 at 7:45
Sorry for my own delay--didn't see this last issue update email. I've just made
a github pull request for the patch I included previously.
Original comment by secreti...@gmail.com
on 15 Jan 2014 at 10:06
test added in a4b486f420635efe18f84445e590c638f28a759c
Original comment by oczk...@gmail.com
on 15 Jan 2014 at 10:43
Original issue reported on code.google.com by
secreti...@gmail.com
on 11 Jan 2013 at 10:00