-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/29/2013 08:37 PM, Stephan Richter wrote: > Well, that's the py3 branch. As Tres mentioned, zodbpickle is ready > for Py3 with noload() support. I totally agree that we do not need to > solve any of the transition work now. > > So for ZODB Py3 support we need to: > > 1. Merge the py3 branch into trunk. 2. Simplify zodbpickle to just > contain the cPickle code that is Py3 compatible. > > I do not care whether this happens for ZODB 4.0 or 4.1 as long as I > get some commitment that 4.1
Chris and I chatted with Jim about this over beers last Friday. I explained that the current 'py3; branch does not require the 'zodbpickle everywhere' stuff (the Python2 side doesn't use 'zodbpickle'). Jim then agreed that we could merge that branch before releasing 4.0. We will need to add some caveats to the docs / changelog (Python3 support is only for new applications, no forward- / backward-compatibility for data, etc.) Given that ZODB won't import or use 'zodbpickle' under Python2, I don't think we need to remove the current Python2 support (as released in 0.4.1): the Python3 version (with noload()) has been there all along. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tsea...@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/ iEYEARECAAYFAlGKfngACgkQ+gerLs4ltQ500gCfQK4HSzemxaYkcPAyleNdkagq MAwAn3wYoCo4BItBHAve4o+lhrzRTBrt =BbCU -----END PGP SIGNATURE----- _______________________________________________ For more information about ZODB, see http://zodb.org/ ZODB-Dev mailing list - ZODB-Dev@zope.org https://mail.zope.org/mailman/listinfo/zodb-dev
