[Python-Dev] 2.7 Release? 2.7 == last of the 2.x line? (original) (raw)
Guido van Rossum guido at python.org
Tue Nov 3 18:38:09 CET 2009
- Previous message: [Python-Dev] 2.7 Release? 2.7 == last of the 2.x line?
- Next message: [Python-Dev] 2.7 Release? 2.7 == last of the 2.x line?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, Nov 3, 2009 at 9:35 AM, ssteinerX at gmail.com <ssteinerx at gmail.com> wrote:
On Nov 3, 2009, at 12:23 PM, Guido van Rossum wrote:
On Tue, Nov 3, 2009 at 9:04 AM, James Y Knight <foom at fuhm.net> wrote:
If that happens, it's not true that there's nowhere to go. A solution would be to discard 3.x as a failed experiment, take everything that is useful from it and port it to 2.x, and simply continue development from the last 2.x release. And from there, features can be deprecated and then removed a few releases later, as is the usual policy. Been there, done that, on a couple other projects. It's unfortunate when you have to throw out work you've done because it failed to gain traction over the thing you tried to replace, but sometimes that's life. I'm not ready for that yet. I think there's plenty of time before we have to agree to such a bleak view. In the mean time let's do something practical like help NumPy port to Py3k. Or, for example, Django...
Wasn't Django ported to Py3k by MvL as a demo? The problem seems to be more to port the Django community to Py3k...
-- --Guido van Rossum (python.org/~guido)
- Previous message: [Python-Dev] 2.7 Release? 2.7 == last of the 2.x line?
- Next message: [Python-Dev] 2.7 Release? 2.7 == last of the 2.x line?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]