Re: Python 2.6
Federico Di Gregorio <fog-NGVKUo/i/[email protected]>
| Newsgroups | gmane.comp.python.db.psycopg.devel |
|---|---|
| Organization | initd.org |
| Message-ID | <[email protected]> |
Il giorno ven, 09/01/2009 alle 11.17 +0900, James Henstridge ha scritto: > On Fri, Jan 9, 2009 at 6:26 AM, Federico Di Gregorio <fog-NGVKUo/i/[email protected]> wrote: > > Try to compile it and report any bugs. I am aboiut to release a > > final version (this weekend probably) before starting the port to > > 3.0 (most of the work was done by Martin, I just need to apply the > > patches to the updated code base and test it). > > I assume we'll still be doing Python 2.x releases of psycopg right? > Having psycopg support Python 3 is great as it is at the base of many > application stacks. However, it is going to take years to get some > stacks ported to Python 3 (e.g. Zope). In that time we'll still need > a database adapter for Python 2.x. Sure. Martin sent me a patch that uses 2to3 to have one version of psycopg support both 2.x and 3. I still have to have a good look at it but seems fine on first sight. > While it is not considered a good idea to try to support both 2.x and > 3.x in Python code, the differences in the C APIs are much smaller. I > wonder if there are things that we could do to the Python 2.x code > base to make it easier to back port fixes/features from the Python 3.x > version? See above. federico -- Federico Di Gregorio http://people.initd.org/fog Debian GNU/Linux Developer [email protected] INIT.D Developer fog-NGVKUo/i/[email protected] Qu'est ce que la folie? Juste un sentiment de liberté si fort qu'on en oublie ce qui nous rattache au monde... -- J. de Loctra _______________________________________________ Psycopg mailing list Psycopg-IAPFreCvJWPBWskQ1e/[email protected] http://lists.initd.org/mailman/listinfo/psycopg
signature.asc
(application/pgp-signature, 197 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEABECAAYFAklnAJ8ACgkQvcCgrgZGjetJxQCgsi4Ft+clG/MAZMUt8nXjDUK6 JtYAnj6avvCSaIMaG8PAPkPoFcONR3Nj =QaY4 -----END PGP SIGNATURE-----