>> http://wiki.python.org/moin/PortingPythonToPy3k >> >> We should discuss first which approach will be the best for PyGreSQL; >> maybe we need to experiment a bit in a separate branch to find out. > > The first two seem like a better option except that they seem to > require dropping <2.6 support.
This is one of the biggest misconceptions about Python 3 support. YOU DO NOT NEED TO DROP 2.3 SUPPORT JUST TO SUPPORT PYTHON 3. In particular, when the page says "Make sure the code runs in Python 2.6", it means "Make sure the code *also* runs in Python 2.6". I've fixed the wiki. My recommendation would be to support 3.x in the current code base. If done correctly, there shouldn't be any significant for 2.x users. Regards, Martin _______________________________________________ PyGreSQL mailing list [email protected] http://mailman.vex.net/mailman/listinfo/pygresql
