pment community is focused
on some imaginary future user base, at the expense of the
much larger current user base. Then again, there's still
plenty of Fortran77 code out there, so...
--Mark Lutz (http://learning-python.com, http://rmi.net/~lutz)
Python users want. If Python core developers want 3.X
to become as popular as 2.X, they should be less concerned with
posts on this list or hands at a conference, than with the feet
of the masses whose votes will ultimately decide 3.X's fate.
--Mark Lutz (http://learning-python.com, http://
t will break their code.
(Yes, sarcasm intended.)
--Mark Lutz (http://learning-python.com, http://rmi.net/~lutz)
> -Original Message-
> From: "Stephen J. Turnbull"
> To: l...@rmi.net
> Subject: Re: [Python-Dev] Patch making the current email package
> (most
ally given the still tentative state of 3.X, stability matters.
--Mark Lutz (http://learning-python.com, http://rmi.net/~lutz)
> -Original Message-
> From: "R. David Murray"
> To: l...@rmi.net
> Subject: Re: [Python-Dev] Patch making the current email package (mo
rticular change's scope
remains to be seen; but to channel most of the users I meet out there
in the real world today: Enough with the 3.X changes already, eh?
--Mark Lutz (http://learning-python.com, http://rmi.net/~lutz)
___
Python-Dev mailin
gh to tip the scales altogether.
--Mark Lutz (http://learning-python.com, http://rmi.net/~lutz)
> -Original Message-
> From: Michael Foord
> To: l...@rmi.net
> Subject: Re: [Python-Dev] email package status in 3.X
> Date: Fri, 18 Jun 2010 18:27:46 +0100
>
> On 18/06/20
nd.
So here it is: The prevailing view is that 3.X developers hoisted things
on users that they did not fully work through themselves. Unicode is
prime among these: for all the talk here about how 2.X was broken in
this regard, the implications of the 3.X string solution remain to be
fully resol
to offer here.
For better or worse, though, this is a personal issue to me too.
After spending much of the last 2 years updating the best selling
Python books for all the changes this group has seen fit to make,
I believe I can say with some authority that 3.X still faces a
very uncertain fut
usly put in an incredible amount of
work on 3.X. As someone who remembers 0.X, though, it's hard not
to find the current situation a bit disappointing.
--Mark Lutz (http://learning-python.com, http://rmi.net/~lutz)
> -Original Message-
> From: l...@rmi.net
> To: "R.
