On 22 January 2011 13:24, Burak Arslan <[email protected]> wrote: > On 01/21/11 09:38, Michael Wood wrote: [...] >> I've only been using soaplib for a couple of months, and it's great, >> but one thing that's a little confusing is the proliferation of >> unfinished branches. i.e 0.8 beta, 1.0 beta, 2.0 alpha, 2.1 beta. >> >> I realise this is probably just because of the history of the project, >> but it would be a lot less confusing if someone could just tag a 1.0 >> final release or something so that someone who wants stable and >> working code (even if it's not guaranteed to be bug free) knows what >> to use. > > https://github.com/arskom/rpclib/tree/soaplib-1.0.0 > http://pypi.python.org/pypi/soaplib/1.0.0 > > https://github.com/arskom/rpclib/tree/soaplib-0.8.2 > http://pypi.python.org/pypi/soaplib/0.8.2 > > http://mail.python.org/pipermail/soap/2010-November/000325.html
Oh, thanks for the info. I see they were released and announced just after I started using soaplib, but before I joined this mailing list, so I didn't know about them. Also, the above tags do not exist in the current soaplib/soaplib repository and did not exist in the arskom/soaplib when I last pulled from it before it disappeared. I see that there's no difference between 1.0.0-beta8 and 1.0.0 release except for the version, so perhaps that should be done in the soaplib/soaplib repository too (e.g. by cherry-picking 2801978f51390772de0ac7ff05f0854dddfdd076 from arskom/rpclib). The situation for 0.8 is the same (see ee25b4c25d23f1f54d86f30103762ae9c7f2e7aa in arskom/rpclib). Then if https://github.com/soaplib/soaplib/downloads is updated (if it doesn't happen automatically) I think that would put this issue to bed :) -- Michael Wood <[email protected]> _______________________________________________ Soap mailing list [email protected] http://mail.python.org/mailman/listinfo/soap
