Re: Python 2.6

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.

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?

The biggest change I've noticed for 3.x is the PyString_* ->
PyBytes_* API renaming.  There are compatibility #defines in Python
2.6, so some of the porting work could probably be done
unconditionally (copying the compat #defines for older Python
releases).

James.