Hi All,
Spine is the vertebral column, the bone on your back that is supposed to
keep you vertical, and the one that houses the neural connections
between your brain and the rest of your body.
https://en.wikipedia.org/wiki/Spine
This spine is a Python library though, so Spyne it is. It seems like
there's a comic character named Spyne, but I doubt it'll cause any
confusion.
As for the Soaplib release, yes Soaplib's deprecated, and no,
soaplib-3.0 won't be compatible with the current
soaplib-2.0.whatever-beta that is currently in pypi. In fact, I imagine
it'll break your existing setups quite badly, as I don't even remember
what soaplib can and can't do. That was a loong time ago.
But, I'd made a promise almost a year ago:
http://mail.python.org/pipermail/soap/2011-September/000526.html
My understanding is that most of you use this package because it offers
decent soap support. So some of you did not really agree with my
transforming soaplib into a general-purpose rpc framework, because
providing abstraction over multiple rpc protocols meant some
soap-specific functionality had to go. (like the @document decorator)
So the plan was to transform soaplib into a spyne wrapper and tuck
soap-specific functionality inside soaplib, and release it as soaplib-3.0.
But of course, that plan is not set in stone. If you'd rather NOT see
another backwards-incompatible soaplib release in pypi, please let the
list know. I'll happily keep my promise of releasing a final stable
soaplib-3.0 that will bring all the recent developments in spyne to the
soaplib namespace, but if nobody wants it, well, I'll be one less thing
to worry about for me :)
Best,
Burak
On 06/25/12 01:16, Raphaël Barrois wrote:
Hi Burak,
Since you're mentioning a new soaplib release here, does it mean there is a
simple upgrade path from soaplib-2.0beta to spyne/soaplib3 ?
I saw your messages stating that soaplib was now deprecated in favor of rpclib,
and thought about making the switch too — we were using soaplib so far, and it
worked well for us, so no real need to upgrade.
Is the new spyne/rpclib/soaplib backwards-compatible with soaplib ? If not, do you
know of a soaplib -> rpclib migration documentation ?
Thanks,
Raphaël BARROIS
On 24 juin 2012, at 23:41, Burak Arslan wrote:
Hi there,
First, I've just renamed rpclib to spyne. No rational reason this time, just
didn't like the ring of rpclib.
I'll of course make sure the rpclib namespace continues to function as it used
to be, so no one should actually notice the name change. I'll also release a
soaplib-3.0.0-rc with spyne-2.8.0-rc
The upcoming release is going to be a release candidate instead of a beta, as
all known bugs are now fixed. I'll issue the release once I'm through with the
docs.
There are also other changes in the pipeline, stay tuned.
Best,
Burak
_______________________________________________
Soap mailing list
[email protected]
http://mail.python.org/mailman/listinfo/soap
_______________________________________________
Soap mailing list
[email protected]
http://mail.python.org/mailman/listinfo/soap
