On Nov 3, 2009, at 4:58 AM, Raymond Hettinger wrote:
P.S. I found it curious that one of the strongest proponents of
killing 2.x also mentioned that he has never written a line of 3.x
code. Since this discussion is a matter of great consequence, I
would hope that advocates will only take informed positions -- this
isn't really time for shooting from the hip and killing 2.x.
Uh, that would be me.
I'm only a proponent of making a decision.
I *want* to have a better development language, library, and add-on
tools.
If 3.x is where future core development time is going to be focused,
then I have faith that they will be able to make it the compelling
path that it will become with Guido having put as much effort into it
as he has. Or, maybe he's completely lost his mind as sometimes
happens with "dictators for life" benevolent or other-wise. ;-)
In any case, splitting time between 2.x and 3.x, with limited
developer resources is going to lead to slower progress on both fronts.
And, as you point out, if 3.x doesn't start getting the crap beat out
of it in the real world sooner rather than later, we may find
ourselves, collectively with a stale 2.x, an under battle-tested 3.x,
and nowhere to go.
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
