On 10/25/10 19:58, Florian Leitner wrote: > Well, it would be most interesting for your head version (the 1.0.0 > beta-8?) naturally, if nobody has done so. So, if currently nobody has > done anything in that direction, maybe I can make some room to look > into it; That would allow me to publish my Twisted asnyc wrapper for > soaplib, too (didn't like the WSGI solution w/o deferreds...). But I > still need to write quite a few missing tests before I feel safe > releasing that into the wild - or into my production code...:). > Currently, it might be a while before that pops up my todo-queue > (work-overload :( ), but I'd really like to move on to Py3, with all > the new nice stuff in it... >
hello florian, if you're after creating transport wrappers for soaplib, i'd suggest you to look at the latest master. some substantial amount of work went into that version so that we could offer a proper api to the people who'd like to do that. once the fix to the issue 49 is merged, (http://github.com/arskom/soaplib/issues#issue/49) the (de)serialization api can be considered stable, imo. there's already support for zeromq and http transports. i think twisted and django wrappers should be next. just let us know when you manage to publish that work. best regards, burak > Cheers, > Florian > > On 25 October 2010 15:51, Burak Arslan <[email protected]> wrote: >> On 10/25/10 13:53, Florian Leitner wrote: >>> Hello everybody, >>> >>> Could anybody quickly let me know if a) soaplib works under Python >>> 3.x, or b) if anybody has successfully used that library after >>> applying 2to3? >>> >> which soaplib is it? >> >> i don't think anybody reported his/her experience with python 3 and >> soaplib. it'd be interesting to hear. >> >> best regards, >> burak >> >> >> _______________________________________________ Soap mailing list [email protected] http://mail.python.org/mailman/listinfo/soap
