On Mon, Apr 28, 2014 at 12:12 PM, Felipe Sateler <fsate...@debian.org> wrote: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732644 > > Reportbug uses debianbts, and debianbts in turn uses soappy. So it all > depends on either porting soappy (and fpconst, used by soappy) to > python3 or porting debianbts away from soappy. > > Both soappy and fpconst seem dead upstream, which makes option 2 more > attractive, but it looks like the soap implementations in python3 do > not get along very well with debbugs, as Jordan notes. > >
I actually tried to do the port to the suds library, and there was more pain than what I noted in the bug report. Suds was a library that I worked with quite a bit in the past, so I thought I would be able to make the port happen, however I never did get suds to make the requests that debbugs expects. If anyone else is willing to give it a try, I am interested in knowing if it is even possible with suds. The issues I ran into are outlined in this stackoverflow post: http://stackoverflow.com/q/21071589/1032785 The underlying issue is that what the debbugs API calls an "array" isn't really an SOAP array. I think the best solution is provide a new version of the debbugs SOAP API that implements proper SOAP types or add REST API. Regards, Jordan Metzmeier -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cad758rgvvtifxciwqdw2irhk0oy6vnjsdfgy7029zotzhoi...@mail.gmail.com
