Re: [Python-Dev] Adding NewType() to PEP 484

2016-06-01 Thread rndblnch
Nick Coghlan gmail.com> writes: > On 31 May 2016 3:12 pm, "Glenn Linderman" g.nevcal.com> wrote: > > On 5/31/2016 12:55 PM, rndblnch wrote: > >> Guido van Rossum gmail.com> writes: > >> > >>> > >>> Also -- the most important

Re: [Python-Dev] Adding NewType() to PEP 484

2016-05-31 Thread rndblnch
Guido van Rossum gmail.com> writes: > > Also -- the most important thing. What to call these things? We're > pretty much settled on the semantics and how to create them (A = > NewType('A', int)) but what should we call types like A when we're > talking about them? "New types" sounds awkward. b

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: > <https://bitbucket.org/rndblnch/cpython-pep380/> 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/mi

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

2011-03-22 Thread rndblnch
so for now it's just a clone of the curent tip. > 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

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