Re: [Python-Dev] Promoting Python 3 [was: PyPy 1.7 - widening the sweet spot]

2011-11-22 Thread Xavier Morel
On 2011-11-23, at 04:51 , Stephen J. Turnbull wrote: > Xavier Morel writes: >> On 2011-11-22, at 17:41 , Stephen J. Turnbull wrote: >>> Barry Warsaw writes: > Hopefully, we're going to be making a dent in that in the next version of Ubuntu. > >>> This is still a big mess in Gentoo and M

Re: [Python-Dev] Promoting Python 3 [was: PyPy 1.7 - widening the sweet spot]

2011-11-22 Thread Ned Deily
In article <87fwhfqywr@uwakimon.sk.tsukuba.ac.jp>, "Stephen J. Turnbull" wrote: > I haven't had the nerve to do this on MacPorts because "port" is such > a flaky thing (not so much port itself, but so many ports assume that > the port maintainer's local configuration is what others' systems u

Re: [Python-Dev] cpython: fix compiler warning by implementing this more cleverly

2011-11-22 Thread Nick Coghlan
On Wed, Nov 23, 2011 at 4:49 PM, Terry Reedy wrote: > I personally strongly prefer the one-line formula to the hardcoded magic > numbers calculated from the formula. I find it much more readable. To me, > the only justification for the switch would be if there is a serious worry > about the kind b

Re: [Python-Dev] cpython: fix compiler warning by implementing this more cleverly

2011-11-22 Thread Terry Reedy
On 11/22/2011 7:42 PM, Benjamin Peterson wrote: 2011/11/22 Antoine Pitrou: On Tue, 22 Nov 2011 16:42:35 -0500 Benjamin Peterson wrote: 2011/11/22 Antoine Pitrou: On Tue, 22 Nov 2011 21:29:43 +0100 benjamin.peterson wrote: http://hg.python.org/cpython/rev/77ab830930ae changeset: 73697:77ab

Re: [Python-Dev] Python 3.4 Release Manager

2011-11-22 Thread Nick Coghlan
On Wed, Nov 23, 2011 at 2:50 PM, Senthil Kumaran wrote: > On Wed, Nov 23, 2011 at 11:50 AM, Larry Hastings wrote: >> I've volunteered to be the Release Manager for Python 3.4.  The FLUFL has > > That's cool.  But just my thought, wouldn't it be better for someone > who regularly commits, fixes bu

Re: [Python-Dev] Python 3.4 Release Manager

2011-11-22 Thread Senthil Kumaran
On Wed, Nov 23, 2011 at 11:50 AM, Larry Hastings wrote: > I've volunteered to be the Release Manager for Python 3.4.  The FLUFL has That's cool. But just my thought, wouldn't it be better for someone who regularly commits, fixes bugs and feature requests be better for a RM role? Once a developer

Re: [Python-Dev] Python 3.4 Release Manager

2011-11-22 Thread Antoine Pitrou
On Tue, 22 Nov 2011 20:27:24 -0800 Raymond Hettinger wrote: > > > > But look! I'm already practicing: NO YOU CAN'T CHECK THAT IN. How's that? > > Needs work? > > You could try a more positive leadership style: THAT LOOKS GREAT, I'M SURE > THE RM FOR PYTHON 3.5 WILL LOVE IT ;-) How about:

Re: [Python-Dev] Python 3.4 Release Manager

2011-11-22 Thread Toshio Kuratomi
On Tue, Nov 22, 2011 at 08:27:24PM -0800, Raymond Hettinger wrote: > > On Nov 22, 2011, at 7:50 PM, Larry Hastings wrote: > > But look! I'm already practicing: NO YOU CAN'T CHECK THAT IN. How's that? > > Needs work? > > You could try a more positive leadership style: THAT LOOKS GREAT, I'M SU

Re: [Python-Dev] Python 3.4 Release Manager

2011-11-22 Thread Raymond Hettinger
On Nov 22, 2011, at 7:50 PM, Larry Hastings wrote: > > > I've volunteered to be the Release Manager for Python 3.4. Awesome. Thanks for stepping up. > The FLUFL has already given it his Sloppy Wet Kiss Of Approval, E! > and we talked to Georg and he was for it too. There's no forma

Re: [Python-Dev] Promoting Python 3 [was: PyPy 1.7 - widening the sweet spot]

2011-11-22 Thread Stephen J. Turnbull
Xavier Morel writes: > On 2011-11-22, at 17:41 , Stephen J. Turnbull wrote: > > Barry Warsaw writes: > >> Hopefully, we're going to be making a dent in that in the next version of > >> Ubuntu. > > This is still a big mess in Gentoo and MacPorts, though. MacPorts > > hasn't done anything ab

[Python-Dev] Python 3.4 Release Manager

2011-11-22 Thread Larry Hastings
I've volunteered to be the Release Manager for Python 3.4. The FLUFL has already given it his Sloppy Wet Kiss Of Approval, and we talked to Georg and he was for it too. There's no formal process for selecting the RM, so I may already be stuck with the job, but I thought it best to pipe up

Re: [Python-Dev] cpython: fix compiler warning by implementing this more cleverly

2011-11-22 Thread Antoine Pitrou
On Tue, 22 Nov 2011 19:42:24 -0500 Benjamin Peterson wrote: > 2011/11/22 Antoine Pitrou : > > On Tue, 22 Nov 2011 16:42:35 -0500 > > Benjamin Peterson wrote: > >> 2011/11/22 Antoine Pitrou : > >> > On Tue, 22 Nov 2011 21:29:43 +0100 > >> > benjamin.peterson wrote: > >> >> http://hg.python.org/cp

Re: [Python-Dev] cpython: fix compiler warning by implementing this more cleverly

2011-11-22 Thread Benjamin Peterson
2011/11/22 Antoine Pitrou : > On Tue, 22 Nov 2011 16:42:35 -0500 > Benjamin Peterson wrote: >> 2011/11/22 Antoine Pitrou : >> > On Tue, 22 Nov 2011 21:29:43 +0100 >> > benjamin.peterson wrote: >> >> http://hg.python.org/cpython/rev/77ab830930ae >> >> changeset:   73697:77ab830930ae >> >> user:  

Re: [Python-Dev] cpython: fix compiler warning by implementing this more cleverly

2011-11-22 Thread Antoine Pitrou
On Tue, 22 Nov 2011 16:42:35 -0500 Benjamin Peterson wrote: > 2011/11/22 Antoine Pitrou : > > On Tue, 22 Nov 2011 21:29:43 +0100 > > benjamin.peterson wrote: > >> http://hg.python.org/cpython/rev/77ab830930ae > >> changeset:   73697:77ab830930ae > >> user:        Benjamin Peterson > >> date:    

Re: [Python-Dev] PyPy 1.7 - widening the sweet spot

2011-11-22 Thread Amaury Forgeot d'Arc
2011/11/22 Terry Reedy > On 11/22/2011 3:28 PM, Philip Jenvey wrote: > > One reason to target 3.2 for now is it's not a moving target. >> > > Neither is the basic design and behavior of the new unicode > implementation. On 3.2 narrow builds, including Windows > > >>> len('\U00010101') > 2 > > Wi

Re: [Python-Dev] cpython: fix wrong credit and issue id given in previous commit

2011-11-22 Thread Giampaolo Rodolà
2011/11/22 Amaury Forgeot d'Arc : > Hi, > 2011/11/22 Giampaolo Rodolà >> >> Sorry, thanks (fixed). > > You also modified Lib/sched.py in the same commit. > Was it intended? If not, please revert it. > -- > Amaury Forgeot d'Arc You're right. I committed sched.py by accident. I'm going to revert i

Re: [Python-Dev] [Python-checkins] cpython: sort last committed name in alphabetical order

2011-11-22 Thread Giampaolo Rodolà
You're right. I committed sched.py by accident. I'm going to revert it. --- Giampaolo http://code.google.com/p/pyftpdlib/ http://code.google.com/p/psutil/ 2011/11/22 Giampaolo Rodolà : > Nope, the commit involving sched was the previous one. > This one was just an unrelated fix. > > --- Giampaolo

Re: [Python-Dev] [Python-checkins] cpython: sort last committed name in alphabetical order

2011-11-22 Thread Giampaolo Rodolà
Nope, the commit involving sched was the previous one. This one was just an unrelated fix. --- Giampaolo http://code.google.com/p/pyftpdlib/ http://code.google.com/p/psutil/ 2011/11/22 Nadeem Vawda : > Did you mean to also modify sched.py in this changeset? >

Re: [Python-Dev] PyPy 1.7 - widening the sweet spot

2011-11-22 Thread Terry Reedy
On 11/22/2011 3:28 PM, Philip Jenvey wrote: One reason to target 3.2 for now is it's not a moving target. Neither is the basic design and behavior of the new unicode implementation. On 3.2 narrow builds, including Windows >>> len('\U00010101') 2 With 3.3, the answer will be, properly, 1. I

Re: [Python-Dev] PyPy 1.7 - widening the sweet spot

2011-11-22 Thread Terry Reedy
On 11/22/2011 10:35 AM, Stefan Behnel wrote: Maciej Fijalkowski, 22.11.2011 15:46: 2011/11/21 Terry Reedy: I strongly recommend that where it makes a difference, the pypy python3 project target 3.3. In particular, don't reproduce the buggy narrow-build behavior of 3.2 and before (perhaps pypy

Re: [Python-Dev] Promoting Python 3 [was: PyPy 1.7 - widening the sweet spot]

2011-11-22 Thread Barry Warsaw
On Nov 22, 2011, at 06:10 PM, Xavier Morel wrote: >It's definitely not going to replace the Apple-provided Python out of the >box, so setting `python` to a python3 is not going to happen. Nor should it! PEP 394 attempts to codify the Python project's recommendations for what version 'python' (e.

Re: [Python-Dev] Promoting Python 3 [was: PyPy 1.7 - widening the sweet spot]

2011-11-22 Thread Barry Warsaw
On Nov 22, 2011, at 09:13 AM, Toshio Kuratomi wrote: >For Fedora (and currently, Red Hat is based on Fedora -- a little more about >that later, though), we have parallel python2 and python3 stacks. Debian (and thus Ubuntu) also has separate Python 2 and 3 stacks. In general, if you have a Python

Re: [Python-Dev] cpython: fix compiler warning by implementing this more cleverly

2011-11-22 Thread Benjamin Peterson
2011/11/22 Antoine Pitrou : > On Tue, 22 Nov 2011 21:29:43 +0100 > benjamin.peterson wrote: >> http://hg.python.org/cpython/rev/77ab830930ae >> changeset:   73697:77ab830930ae >> user:        Benjamin Peterson >> date:        Tue Nov 22 15:29:32 2011 -0500 >> summary: >>   fix compiler warning by

Re: [Python-Dev] cpython: fix compiler warning by implementing this more cleverly

2011-11-22 Thread Antoine Pitrou
On Tue, 22 Nov 2011 21:29:43 +0100 benjamin.peterson wrote: > http://hg.python.org/cpython/rev/77ab830930ae > changeset: 73697:77ab830930ae > user:Benjamin Peterson > date:Tue Nov 22 15:29:32 2011 -0500 > summary: > fix compiler warning by implementing this more cleverly You

Re: [Python-Dev] PyPy 1.7 - widening the sweet spot

2011-11-22 Thread Amaury Forgeot d'Arc
2011/11/22 Philip Jenvey > One reason to target 3.2 for now is it's not a moving target. There's > overhead involved in managing modifications to the pure python standard lib > needed for PyPy, tracking 3.3 changes as they happen as well exacerbates > this. > > The plans to split the standard lib

Re: [Python-Dev] cpython: fix wrong credit and issue id given in previous commit

2011-11-22 Thread Amaury Forgeot d'Arc
Hi, 2011/11/22 Giampaolo Rodolà > Sorry, thanks (fixed). > You also modified Lib/sched.py in the same commit. Was it intended? If not, please revert it. -- Amaury Forgeot d'Arc ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org

Re: [Python-Dev] PyPy 1.7 - widening the sweet spot

2011-11-22 Thread Philip Jenvey
On Nov 22, 2011, at 7:35 AM, Stefan Behnel wrote: > Maciej Fijalkowski, 22.11.2011 15:46: >> PyPy's py3k branch targets Python 3.2 until 3.3 is released and very >> likely 3.3 afterwards. Optimizations are irrelevant really in the case >> of PyPy. > > I admit that I wasn't very clear in my wordi

Re: [Python-Dev] [Python-checkins] cpython: sort last committed name in alphabetical order

2011-11-22 Thread Nadeem Vawda
Did you mean to also modify sched.py in this changeset? ___ 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

Re: [Python-Dev] cpython: fix wrong credit and issue id given in previous commit

2011-11-22 Thread Giampaolo Rodolà
Sorry, thanks (fixed). --- Giampaolo http://code.google.com/p/pyftpdlib/ http://code.google.com/p/psutil/ 2011/11/22 Antoine Pitrou : > On Tue, 22 Nov 2011 13:38:03 +0100 > giampaolo.rodola wrote: >> diff --git a/Misc/ACKS b/Misc/ACKS >> --- a/Misc/ACKS >> +++ b/Misc/ACKS >> @@ -11,7 +11,7 @@ >>

Re: [Python-Dev] Promoting Python 3 [was: PyPy 1.7 - widening the sweet spot]

2011-11-22 Thread David Malcolm
On Tue, 2011-11-22 at 09:13 -0800, Toshio Kuratomi wrote: > On Wed, Nov 23, 2011 at 01:41:46AM +0900, Stephen J. Turnbull wrote: > > Barry Warsaw writes: > > > > > Hopefully, we're going to be making a dent in that in the next version of > > > Ubuntu. > > > > This is still a big mess in Gentoo

Re: [Python-Dev] Promoting Python 3 [was: PyPy 1.7 - widening the sweet spot]

2011-11-22 Thread Toshio Kuratomi
On Wed, Nov 23, 2011 at 01:41:46AM +0900, Stephen J. Turnbull wrote: > Barry Warsaw writes: > > > Hopefully, we're going to be making a dent in that in the next version of > > Ubuntu. > > This is still a big mess in Gentoo and MacPorts, though. MacPorts > hasn't done anything about ceating a t

Re: [Python-Dev] Promoting Python 3 [was: PyPy 1.7 - widening the sweet spot]

2011-11-22 Thread Xavier Morel
On 2011-11-22, at 17:41 , Stephen J. Turnbull wrote: > Barry Warsaw writes: >> Hopefully, we're going to be making a dent in that in the next version of >> Ubuntu. > > This is still a big mess in Gentoo and MacPorts, though. MacPorts > hasn't done anything about ceating a transition infrastructur

[Python-Dev] Promoting Python 3 [was: PyPy 1.7 - widening the sweet spot]

2011-11-22 Thread Stephen J. Turnbull
Barry Warsaw writes: > Hopefully, we're going to be making a dent in that in the next version of > Ubuntu. This is still a big mess in Gentoo and MacPorts, though. MacPorts hasn't done anything about ceating a transition infrastructure AFAICT. Gentoo has its "eselect python set VERSION" stuff,

Re: [Python-Dev] cpython: fix wrong credit and issue id given in previous commit

2011-11-22 Thread Antoine Pitrou
On Tue, 22 Nov 2011 13:38:03 +0100 giampaolo.rodola wrote: > diff --git a/Misc/ACKS b/Misc/ACKS > --- a/Misc/ACKS > +++ b/Misc/ACKS > @@ -11,7 +11,7 @@ > PS: In the standard Python distribution, this file is encoded in UTF-8 > and the list is in rough alphabetical order by last names. > > -Mat

Re: [Python-Dev] PyPy 1.7 - widening the sweet spot

2011-11-22 Thread Stefan Behnel
Maciej Fijalkowski, 22.11.2011 15:46: On Tue, Nov 22, 2011 at 3:15 PM, Stefan Behnel wrote: Giampaolo Rodolà, 22.11.2011 10:21: 2011/11/21 Terry Reedy: I strongly recommend that where it makes a difference, the pypy python3 project target 3.3. In particular, don't reproduce the buggy narrow-b

Re: [Python-Dev] PyPy 1.7 - widening the sweet spot

2011-11-22 Thread Barry Warsaw
On Nov 22, 2011, at 02:15 PM, Stefan Behnel wrote: >Well, Py3 still has a lot to catch up in terms of wide spread distribution >compared to Py2.x, and new users will usually start using the most up to date >release, which will soon be 3.3. > >Besides, 3.3 has received various optimisations that ma

Re: [Python-Dev] PyPy 1.7 - widening the sweet spot

2011-11-22 Thread Maciej Fijalkowski
On Tue, Nov 22, 2011 at 3:15 PM, Stefan Behnel wrote: > Giampaolo Rodolà, 22.11.2011 10:21: >> >> 2011/11/21 Terry Reedy: >>> >>> I strongly recommend that where it makes a difference, the pypy python3 >>> project target 3.3. In particular, don't reproduce the buggy narrow-build >>> behavior of 3.

Re: [Python-Dev] PyUnicode_Resize

2011-11-22 Thread Amaury Forgeot d'Arc
2011/11/22 Victor Stinner > Hi, > > In Python 3.2, PyUnicode_Resize() expects a number of Py_UNICODE units, > whereas Python 3.3 expects a number of characters. > > It is tricky to convert a number of Py_UNICODE units to a number of > characters, so it is diffcult to provide a backward compatibil

Re: [Python-Dev] PyPy 1.7 - widening the sweet spot

2011-11-22 Thread Stefan Behnel
Giampaolo Rodolà, 22.11.2011 10:21: 2011/11/21 Terry Reedy: I strongly recommend that where it makes a difference, the pypy python3 project target 3.3. In particular, don't reproduce the buggy narrow-build behavior of 3.2 and before (perhaps pypy avoids this already). Do include the new unicode

Re: [Python-Dev] PyUnicode_EncodeDecimal

2011-11-22 Thread Victor Stinner
Le mardi 22 novembre 2011 02:02:05, Victor Stinner a écrit : > This function is broken by design if an error handler is specified: the > caller cannot know the size of the output buffer, whereas the caller has > to allocate this buffer. > > I propose to raise an error if an error handler (differen

Re: [Python-Dev] PyUnicode_EncodeDecimal

2011-11-22 Thread Stefan Krah
Victor Stinner wrote: > > Should we document and test it, leave it unchanged and > > deprecate it, or simply remove it? > > If we change PyUnicode_EncodeDecimal() to reject error handlers different > than > strict, we can keep this function for some release and deprecate it. The > function is

Re: [Python-Dev] PyPy 1.7 - widening the sweet spot

2011-11-22 Thread Giampaolo Rodolà
2011/11/21 Terry Reedy : > I strongly recommend that where it makes a difference, the pypy python3 > project target 3.3. In particular, don't reproduce the buggy narrow-build > behavior of 3.2 and before (perhaps pypy avoids this already). Do include > the new unicode capi in cpyext. I anticipate t