Re: git branches reorganization

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Federico Di Gregorio wrote:
> The work done by Jan and Daniele on async made completely obsolete my
> tentative port of psycopg to python3. That is, the master branch is not
> the real master anymore (to be sincere, it wasn't the real master even
> before that..) But simply swapping python2 for master will confuse a lot
> of people already tracking the repository, so here's my plan:
> 
> 1) move master -> python3-historical
> 2) leave python2 as is
> 
> If me or someone else want to revive the python3 port we'll branch from
> python2 into a new python3 branch (that's why the old port is named
> python3-historical) and continue from there.
> 
> If, and only if, the codebase will be able to support python2 and
> python3 at the same time we'll merge them in a single master branch in
> the future.

Supporting both Python2 and Python3 from a common codebase seems like a
good goal, and one worth investing a bit of time upfront.  The Zope
Toolkit project has had some success in using the '2_to_3' support in
the 'distribute' analog / replacement for setuptools, which allows the
project to be converted on-the-fly to Python3-compatible syntax
(sometimes with extra fixers).

Doctests have been the biggest conversion pain, to date.  Lennart
Regebro has done a bunch of the work, and blogged about it:  his blog
would be worth a read:

  http://regebro.wordpress.com/category/python3/



Tres.
- --
===================================================================
Tres Seaver          +1 540-429-0999          [email protected]
Palladion Software   "Excellence by Design"    http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkvu3GUACgkQ+gerLs4ltQ5/vACeN8NDL/7YvTKP8Gb7VmSJDaQl
4ZoAn2Nl7HikyIKCIo6Nj/8NPkbJ3Z8U
=V+RZ
-----END PGP SIGNATURE-----