[Python-3000] Py3k release schedule worries (original) (raw)

Fredrik Lundh fredrik at pythonware.com
Tue Dec 19 19:52:54 CET 2006

Guido van Rossum wrote:

an alternative would be to move concrete 3.0-related implementation discussions back to python-dev, and keep this list for Python 3.0 PEP work and "year 3000" stuff. But that's confusing since the 3.0 PEP work is also concrete implementation related (at least in my mind it is supposed to be -- no proposal will be accepted unless it's clear how it can be implemented).

so keep it here while the details are being hammered out, and move it over to python-dev when it's time to start working on it (and move it back if it turns out that it wasn't ready, after all).

after all, lots of 3.X stuff can go into 2.X anyway (especially after your pronouncements earlier today), and I think it's better to keep code-related activities in one place.

And there are plenty of developers on python-dev who prefer to stick to python 2.6 work.

yeah, but there are also plenty of people who want to contribute concrete things to Python, but don't have a clue where to start. the current situation is something of a mess. I fear that adding yet another forum will make things even messier.

More information about the Python-3000 mailing list