[ZODB-Dev] RFC: Python2 - Py3k database compatibility
Tres Seaver
tseaver at palladion.com
Mon Apr 29 16:25:12 UTC 2013
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 04/29/2013 11:00 AM, Jim Fulton wrote:
> Let's keep master stable. Maybe someone will want to add features
> before the Python 3 support is stable. I don't want to hold 4.1
> hostage either.
Given that the only folks (besides maybe you) invested in ZODB
development want Py3k support ASAP. I don't see that. Do you have
features in mind that you would imagine releasing before we land Py3k
support?
> I suggest breaking the Python 3 work into increments that can each be
> introduced without sacrificing stability.
>
> The first increment could provide Python 3 support without any
> conversion or compatibility support. This is something you could
> probably achieve pretty quickly and would allow you meet your
> immediate goals.
We are already there, AFAIK, on the 'py3' branch: the blocker is just
getting out a release.
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+nugACgkQ+gerLs4ltQ4lmACgmfAMS0tqV86+v0ItIlbMkhtK
i6gAoLPO4aehpHIrZokPG8c4hRIAOsnE
=6f/j
-----END PGP SIGNATURE-----
More information about the ZODB-Dev
mailing list