On Nov 3, 2009, at 12:38 PM, Guido van Rossum wrote:
On Tue, Nov 3, 2009 at 9:35 AM, sstein...@gmail.com <sstein...@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 <f...@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...
I do remember seeing something about that somewhere but it sure isn't
jumping into my workflow at the moment.
If I can get a Python 3 version of Django, that's keeping up with
trunk, I hereby declare that I will start using it on my current
project as soon as the client takes the blowtorch off my toes for the
current deliverable.
And...I'll help keep it up to date with trunk as best I can and also
help pull along all the modules I need (incidentally, including
Beautiful Soup).
I really _want_ Python 3 to be better, I hope actual use convinces me
that it is...
There, now I'm committed (or, maybe I should _be_ committed).
Thanks,
S
_______________________________________________
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/archive%40mail-archive.com
