[ZODB-Dev] RFC: Python2 - Py3k database compatibility
Tres Seaver
tseaver at palladion.com
Mon Apr 29 14:20:42 UTC 2013
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 04/29/2013 09:48 AM, Jim Fulton wrote:
> On Sun, Apr 28, 2013 at 8:34 PM, Stephan Richter
> <stephan.richter at gmail.com> wrote:
>> On Sunday, April 28, 2013 07:23:12 PM Jim Fulton wrote:
>>> Can ZODB 4 be used now without zodbpickle?
>>
>> No, unfortunately for Py2 we need the custom cPickle and for Py3
>> `noload()` support (as Tres mentioned).
>
> This is a problem.
>
> The only change in ZODB 4.0 was supposed to be the breakup.
>
> This was supposed to be a low-risk release. The separation into
> multiple packages was supposed to increase agility, but now it appears
> we're stuck.
The only reason we had delayed the 4.0 release (in my mind, anyway) was
that it was a good way to signal the Py3k compatibliity changes. I'm not
wedded to calling the Py3k-compatible release "4.0".
> I'd like there to a stable 4.0 release **soon** that doesn't use
> zodbpickle for Python 2.
>
> For now, I suggest we focus on stability and the ability to make
> progress on non-Python-3-related work.
>
> After that is achieved, I suggest we get to the point where people
> can create new databases and use them with Python 3. We need to do
> this without hindering the ability to make new stable releases.
The trunk of the 'ZODB' package does not have any of the Py3k /
zodbpickle changes yet. We could make a ZODB 4.0b1 release from the
trunk today and create a '4.0' stable branch prior to any merge of the
'py3' work.
> As far as the grander vision for Python2/3 transition and
> interoperability, we need to make progress incrementally and not
> sacrifice stability of the master branch.
>
> I made the 3.11 release fully expecting a stable 4.0 release soon.
That was of the 'ZODB3' meta-package, right?
Tres.
- --
===================================================================
Tres Seaver +1 540-429-0999 tseaver at palladion.com
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
iEYEARECAAYFAlF+gboACgkQ+gerLs4ltQ4+7wCg222VrN5b0jkRrSJKVBL1VEBr
5lgAoINrzLbTus6ycBXcVGovxWIPBQ5t
=XLcz
-----END PGP SIGNATURE-----
More information about the ZODB-Dev
mailing list