Re: [ZODB-Dev] RFC: Python2 - Py3k database compatibility

2013-05-10 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/08/2013 12:34 PM, Tres Seaver wrote: 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

Re: [ZODB-Dev] RFC: Python2 - Py3k database compatibility

2013-05-10 Thread Jim Fulton
On Fri, May 10, 2013 at 5:04 PM, Tres Seaver tsea...@palladion.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/08/2013 12:34 PM, Tres Seaver wrote: 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

Re: [ZODB-Dev] RFC: Python2 - Py3k database compatibility

2013-05-10 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/10/2013 07:55 PM, Stephan Richter wrote: On Friday, May 10, 2013 05:04:31 PM Tres Seaver wrote: I pushed out a ZODB 4.0.0b1 release after the merge. If the buildbots stay green over the weekend, I think we can release a 4.0.0 final early

Re: [ZODB-Dev] RFC: Python2 - Py3k database compatibility

2013-05-10 Thread Stephan Richter
On Friday, May 10, 2013 11:01:33 PM Tres Seaver wrote: Tres, are we ready to commit to a zope.security 4.0.0 as well? AFAIK, we could cut it from the 'master' at any time. I don't know of any issues I don't see any open launchpad issues which should block a release. Cool, we can do that