Hi all.
I was looking into suds a bit and found the development to either be slowish or I was just unlucky and did not run into the correct developers.
I tried but could not find any active enough project repositories so I prepared a Mercurial repository at 'https://bitbucket.org/jurko/suds' containing some of my patches - for now mostly concentrating on preparing a more detailed test suite as I research suds. For other topics I'd like to change/add in the suds library itself - I'll post separate messages to the mailing list.
I also helped update the Py3 patch series a bit (hosted at 'https://bitbucket.org/bernh/suds-python-3-patches'). It has a few more Py3 related fixes, can now be applied on top of my repository and the original suds one and its results are still compatible with Py2.
Is there any chance for such changes to be accepted back into the original project repository and how should one go about it? Or how to at least get feedback on what else needs to be done for them to be accepted?
Is there any interest at all for such further suds library development? Or should I just keep my work for private use?
Best regards, Jurko Gospodnetić
Hi, I also worked on SUDS, and sent some of my patches to this list in May, but got no response. I worked on WS-Security, implemented correct, standards- compliant digest UsernameToken support, and will publish DigitalSignature soon. Currently, these are available in my GitHub repositories (https://github.com/dnet/suds and https://github.com/dnet/SudsSigner), and I've written my masters thesis about it (http://vsza.hu/thesis-beta.pdf). There are also patches based on my work regarding MTOM attachments, available in the GH repository of Zbigniew Siciarz (https://github.com/zsiciarz/suds).
By looking at the archives of 2011, there were mutliple threads about the future of SUDS development, and IIRC the maintainer hasn't responded to any of these. One of these threads asks in the subject "Is suds still maintained?", and I think, although maintenance in the regular sense is missing, it's worth posting the patches, as you might never know, who can make use of it -- a great example is Antonia Valentin (2011.10.19. "digest in header"), who also missed digest UsernameToken support, and my patches solved the problem.
Regards, András Veres-Szentkirályi
2011. december 18. vasárnap 12:49:41 dátummal Jurko Gospodnetić ezt írta:
Hi all.
I was looking into suds a bit and found the development to either be slowish or I was just unlucky and did not run into the correct developers.
I tried but could not find any active enough project repositories so I prepared a Mercurial repository at 'https://bitbucket.org/jurko/suds' containing some of my patches - for now mostly concentrating on preparing a more detailed test suite as I research suds. For other topics I'd like to change/add in the suds library itself - I'll post separate messages to the mailing list.
I also helped update the Py3 patch series a bit (hosted at 'https://bitbucket.org/bernh/suds-python-3-patches'). It has a few more Py3 related fixes, can now be applied on top of my repository and the original suds one and its results are still compatible with Py2.
Is there any chance for such changes to be accepted back into the original project repository and how should one go about it? Or how to at least get feedback on what else needs to be done for them to be accepted?
Is there any interest at all for such further suds library development? Or should I just keep my work for private use?
Best regards, Jurko Gospodnetić
Hi all.
I tried but could not find any active enough project repositories so I prepared a Mercurial repository at 'https://bitbucket.org/jurko/suds' containing some of my patches - for now mostly concentrating on preparing a more detailed test suite as I research suds. For other topics I'd like to change/add in the suds library itself - I'll post separate messages to the mailing list.
--- Update on what has been done so far in my suds library project fork.
* Cleaned up the test suite a bit. * Separated automated tests and 'quasi-tests' that are actually just Python scripts someone could use to manually test suds by tweaking them and reading through their output. * Ported the one existing automated unit test script to use the pytest unit test framework (better infrastructure + fixes problems with running the test from an unexpected folder or having another set of suds library sources already on the Python module search path, e.g. installed). * Fixed DateTimeTest.testOverflow test code problems caused by that test case depending on a global Timezone.LOCAL setting left behind by other tests. * Added additional tests.
* Added support for operations taking choice parameters (based on a patch by michaelgruenewald & bennetb01 attached to ticket #342).
* Code base compatible with Py3 patches hosted at 'https://bitbucket.org/bernh/suds-python-3-patches' and all tests seem to run and no manually tested code triggered any problems in the following scenarios: * Python 2 without Py3 patches applied. * Python 2 with Py3 patches applied. * Python 3 with Py3 patches applied.
* Corrected accessing suds.xsd.sxbase.SchemaObject subitems by index (see 'http://fedorahosted.org/suds/ticket/420').
--- Some questions for whomever can offer assistance. :-)
Anyone want to contribute his own work on suds to this or wants to integrate this into some already existing and actively developed code base?
Anyone wants to help write additional tests? Or has his own tests tucked away somewhere that he would like to contribute?
Any suggestions on what would be the easiest way to implement the following test types: * Tests for constructing SOAP requests. * Tests for parsing SOAP responses. * Tests requiring an actual running web service. * For example, I want to add support for connecting to a web service using HTTPS with client certificate authentication (already implemented and used in an actual end-user application using suds but I'd like to push this change back to suds and add tests for it). * Any suggestions on the best lightweight framework for implementing such a test web service?
--- Next steps.
I'll prepare a new forked suds distribution now containing all the changes (need it internally so other projects do not depend on suds library development sources). If there is any interest I can publish it publicly (PyPI?). Disclaimer: I would like it best if I did not need to do a separate distribution and could get all of this integrated into the main development repository but it seems I can not wait for that and need some 'clean milestones' developed at a much greater pace than observed in the current official development.
Best regards, Jurko Gospodnetić
Hi all.
I'll prepare a new forked suds distribution now containing all the changes (need it internally so other projects do not depend on suds library development sources). If there is any interest I can publish it publicly (PyPI?). Disclaimer: I would like it best if I did not need to do a separate distribution and could get all of this integrated into the main development repository but it seems I can not wait for that and need some 'clean milestones' developed at a much greater pace than observed in the current official development.
I just prepared the initial version distribution release and uploaded it as 'suds-jurko' to PyPI.
Any further suggestions/assistance/ideas/wishes/reviews welcome. :-)
Best regards, Jurko Gospodnetić
Hi all.
I just prepared the initial version distribution release and uploaded it as 'suds-jurko' to PyPI.
Heh, didn't take long to find a problem with the initial release. :-( Printing out a suds.client.Client object failed with IndexError due to some 'undocumented' expectations on how the suds.__build__ string should be formatted.
Now corrected and a second release pushed out. Sorry for the inconvenience and Merry Christmas everyone... :-)
Best regards, Jurko Gospodnetić
-
Jurko Gospodnetić -
Veres-Szentkiralyi Andras