Re: [Python-Dev] Let's get PEP 380 into Python 3.3

2011-03-25 Thread Nick Coghlan
On Sat, Mar 26, 2011 at 6:25 AM, rndblnch wrote: > The raw path is visible there: > > and I have documented how to use it on the wiki: > > > I will stop spamming python-dev now... >

Re: [Python-Dev] Let's get PEP 380 into Python 3.3

2011-03-25 Thread rndblnch
rndblnch gmail.com> writes: > Now that I have figured out how to use patch queues with bitbucket, I will > maintain greg's pep380 implementation as a patch on top of cpython here: > snip > The patch is now visible here: >

Re: [Python-Dev] Let's get PEP 380 into Python 3.3

2011-03-24 Thread rndblnch
rndblnch gmail.com> writes: > > Anyone without push rights for hg.python.org may want to fork the > > mirror the bitbucket folks set up during the PyCon sprints to avoid > > having to push the whole repository up to a separate hosting site: > > https://bitbucket.org/mirror/cpython > > Done here:

Re: [Python-Dev] Let's get PEP 380 into Python 3.3

2011-03-22 Thread Nick Coghlan
On Tue, Mar 22, 2011 at 10:06 PM, rndblnch wrote: > Sorry to have done that, once again, I was not expecting to actually have the > rights to cause any side-effect on . I guess that it > may > not be desirable to allow anyone do such server-side clone. Unmodified clones do

Re: [Python-Dev] Let's get PEP 380 into Python 3.3

2011-03-22 Thread rndblnch
Nick Coghlan gmail.com> writes: > On Tue, Mar 22, 2011 at 9:21 AM, Guido van Rossum python.org> wrote: > > In the light of the recent discussion about Hg clones, perhaps you > > could make this a server-side clone so it's easier for others to play > > along? I don't have push rights so I can no

Re: [Python-Dev] Let's get PEP 380 into Python 3.3

2011-03-22 Thread Nick Coghlan
On Tue, Mar 22, 2011 at 9:21 AM, Guido van Rossum wrote: > In the light of the recent discussion about Hg clones, perhaps you > could make this a server-side clone so it's easier for others to play > along? Anyone without push rights for hg.python.org may want to fork the mirror the bitbucket fol

Re: [Python-Dev] Let's get PEP 380 into Python 3.3

2011-03-21 Thread Guido van Rossum
On Mon, Mar 21, 2011 at 4:06 PM, rndblnch wrote: > Greg Ewing canterbury.ac.nz> writes: >> Guido van Rossum wrote: >> > Ok. Will you hvae time to port your patches to 3.3? >> I'm not sure -- I'll see what I can do. > > If this can help, I have written a script that transforms greg's patch into a

Re: [Python-Dev] Let's get PEP 380 into Python 3.3

2011-03-21 Thread rndblnch
Greg Ewing canterbury.ac.nz> writes: > Guido van Rossum wrote: > > Ok. Will you hvae time to port your patches to 3.3? > I'm not sure -- I'll see what I can do. If this can help, I have written a script that transforms greg's patch into a patch that applies on cpython current tip. The script is a

Re: [Python-Dev] Let's get PEP 380 into Python 3.3

2011-03-08 Thread rndblnch
Greg Ewing canterbury.ac.nz> writes: > > Guido van Rossum wrote: > > Ok. Will you hvae time to port your patches to 3.3? > > I'm not sure -- I'll see what I can do. > If this can help, I've "ported" the patch YieldFrom-Python3.1.2-rev5.patch against current cpython tip. What I've done: - clon

Re: [Python-Dev] Let's get PEP 380 into Python 3.3

2011-02-27 Thread Greg Ewing
Guido van Rossum wrote: Ok. Will you hvae time to port your patches to 3.3? I'm not sure -- I'll see what I can do. -- Greg ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail

Re: [Python-Dev] Let's get PEP 380 into Python 3.3

2011-02-25 Thread Joao S. O. Bueno
On Fri, Feb 25, 2011 at 8:01 PM, Greg Ewing wrote: > From: Guido van Rossum > >> (OTOH I am not much enamored with cofunctions, PEP 3152.) > > That's okay, I don't like it much myself in its current form. > I plan to revisit it at some point, but there's no hurry. I've just gone through PEP 3152

Re: [Python-Dev] Let's get PEP 380 into Python 3.3

2011-02-25 Thread Jesse Noller
On Fri, Feb 25, 2011 at 5:43 PM, Guido van Rossum wrote: > Now that the language moratorium is lifted, let's make sure to get PEP > 380 implemented for Python 3.3. I think there are some minor issues to > be resolved, but I don't think that should stop someone from doing a > first pass of the impl

Re: [Python-Dev] Let's get PEP 380 into Python 3.3

2011-02-25 Thread Guido van Rossum
Ok. Will you hvae time to port your patches to 3.3? On Fri, Feb 25, 2011 at 3:01 PM, Greg Ewing wrote: > From: Guido van Rossum > >> (OTOH I am not much enamored with cofunctions, PEP 3152.) > > That's okay, I don't like it much myself in its current form. > I plan to revisit it at some point, bu

Re: [Python-Dev] Let's get PEP 380 into Python 3.3

2011-02-25 Thread Greg Ewing
From: Guido van Rossum > (OTOH I am not much enamored with cofunctions, PEP 3152.) That's okay, I don't like it much myself in its current form. I plan to revisit it at some point, but there's no hurry. -- Greg This email may be confidential and subject to legal privilege, it may not reflect

[Python-Dev] Let's get PEP 380 into Python 3.3

2011-02-25 Thread Guido van Rossum
Now that the language moratorium is lifted, let's make sure to get PEP 380 implemented for Python 3.3. I think there are some minor issues to be resolved, but I don't think that should stop someone from doing a first pass of the implementation (especially since a version for 2.6 already exists). (