In addition to the breakages because of Python 3.0 features and bugs, there currently isn't a way to deal with most of those breakages, except by forking your code in 2.x and 3.x versions. You can't write a non-bare except statement that works in 2.x and 3.x, for instance. I'd say it's still too early, but we're getting there -- most of the 3.0 features are in, and the 2.6-compatibility-mode is being worked on (slowly, but still.) When they're in, people could have a buildbot setup that tests the same source in 3.0-to-be and 2.6-to-be (and older released Python versions, if they really want to see a lot of errors.) such a setup would probably catch a lot of 3.0and 2.6 bugs, too ;-) On 2/13/07, "Martin v. Löwis" <martin@v.loewis.de> wrote:
Grig Gheorghiu schrieb:
So is there any value or interest in setting up a svn notification hook for py3k commits that would go to the pybots buildbot master?
A similar question is whether there should be buildbots for Python 3 itself (i.e. running the test suite). Even for that, it was considered too early.
I would expect that packages break in massive ways because of the by-design incompatibilities. It would be good to get an estimate of what the impact is, but having a build once a month might be more than enough. To fully study the problems, one has to install Python 3 locally, anyway, and then run the package in question on top of that.
Regards, Martin _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/thomas%40python.org
-- Thomas Wouters <thomas@python.org> Hi! I'm a .signature virus! copy me into your .signature file to help me spread!