On 25 Jun 2014 07:05, "Ethan Furman" wrote:
>
> On 06/24/2014 12:54 PM, Ned Deily wrote:
>>
>>
>> Yes, we are committed to maintaining
>> Python 2.7 for multiple years but that doesn't mean we have to fix every
>> open issue or even most open issues. Any or all of the above costs may
>> apply to
On 6/24/2014 4:22 AM, Serhiy Storchaka wrote:
> I submitted a number of patches which fixes currently broken
> Unicode-disabled build of Python 2.7 (built with --disable-unicode
> configure option). I suppose this was broken in 2.7 when C
> implementation of the io module was introduced.
It has
On 06/24/2014 12:54 PM, Ned Deily wrote:
Yes, we are committed to maintaining
Python 2.7 for multiple years but that doesn't mean we have to fix every
open issue or even most open issues. Any or all of the above costs may
apply to any changes we make. For many of our users, the best
maintenanc
In article
<1403625970.6550.133062453.693ec...@webmail.messagingengine.com>,
Benjamin Peterson wrote:
> If Serhiy wants to spend his time supporting this arcane feature, he can
> do that. It doesn't really seem worth risking regressions to do this,
> though.
That's why I'm concerned about apply
On Tue, 24 Jun 2014 20:43:41 +0200, francis wrote:
> On 06/24/2014 03:50 AM, Ezio Melotti wrote:
> >>From the first graph you can see that out of the 4500+ open issues,
> > about 2000 have a patch.
> One would like to start with the ones that are bugs ;-) and see some
> status line trying to drop
On 06/24/2014 03:50 AM, Ezio Melotti wrote:
From the first graph you can see that out of the 4500+ open issues,
about 2000 have a patch.
One would like to start with the ones that are bugs ;-) and see some
status line trying to drop to 0 (is that possible :-) ?)
We need more reviewers and com
If Serhiy wants to spend his time supporting this arcane feature, he can
do that. It doesn't really seem worth risking regressions to do this,
though.
On Tue, Jun 24, 2014, at 01:55, Victor Stinner wrote:
> Hi,
>
> I don't know anyone building Python without Unicode. I would prefer to
> modify co
On 6/24/2014 4:22 AM, Serhiy Storchaka wrote:
I submitted a number of patches which fixes currently broken
Unicode-disabled build of Python 2.7 (built with --disable-unicode
configure option). I suppose this was broken in 2.7 when C
implementation of the io module was introduced.
http://bugs.pyt
24.06.14 14:50, Victor Stinner написав(ла):
2014-06-24 13:04 GMT+02:00 Skip Montanaro :
I can't see any reason to make a backwards-incompatible change to
Python 2 to only support Unicode. You're bound to break somebody's
setup. Wouldn't it be better to fix bugs as Serhiy has done?
According to
2014-06-24 13:04 GMT+02:00 Skip Montanaro :
> I can't see any reason to make a backwards-incompatible change to
> Python 2 to only support Unicode. You're bound to break somebody's
> setup. Wouldn't it be better to fix bugs as Serhiy has done?
According to the long list of issues, I don't think th
Le 24/06/2014 07:04, Skip Montanaro a écrit :
I can't see any reason to make a backwards-incompatible change to
Python 2 to only support Unicode. You're bound to break somebody's
setup.
Apparently, that setup would already have been broken for years.
Regards
Antoine.
___
I can't see any reason to make a backwards-incompatible change to
Python 2 to only support Unicode. You're bound to break somebody's
setup. Wouldn't it be better to fix bugs as Serhiy has done?
Skip
___
Python-Dev mailing list
Python-Dev@python.org
https
Hi,
I don't know anyone building Python without Unicode. I would prefer to
modify configure to raise an error, and drop #ifdef in the code. (Stop
supporting building Python 2 without Unicode.)
Building Python 2 without Unicode support is not an innocent change.
Python is moving strongly to Unicod
I submitted a number of patches which fixes currently broken
Unicode-disabled build of Python 2.7 (built with --disable-unicode
configure option). I suppose this was broken in 2.7 when C
implementation of the io module was introduced.
http://bugs.python.org/issue21833 -- main patch which fixes
14 matches
Mail list logo