On Friday, 24 July, 2009, at 03:59PM, "Leonardo Santagada"
On Jul 24, 2009, at 10:29 AM, Lennart Regebro wrote:
2009/7/24 Tarek Ziadé
: I can postpone the 0.6 release for a week or so, until this is ready, so we can have 0.6 for Python 3.
I think we should make a 2.x only release first. The changes to support Python 3 are small but numerous and since the test-coverage isn't that great I'm worried it will insert subtle bugs. I would be less worried if we can have a longer test-period after these changes.
On the other hand, if we do merge these changes before the 0.6 release they will quickly get tested. ;)
People using python 3x don't have support for setuptools so they would understand if you release early a beta version. And I think you should, not having setutools is a problem for every package being converted to python 3.1
The issue with merging python3-related changes is not that the python3 port would have a beta-status, but that there is a risk that this will accidently break python2 support. I agree with Lennart that a 2.x only release would be better, especially because it would be possible to do a 0.7 alpha/beta release short after the stable 0.6 release. Ronald
-- Leonardo Santagada santagada at gmail.com
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig