Re: [Python-Dev] PyGC_Collect ignores state of `enabled`

Hi, I intended for gc.collect() to actually collect cycles even if the auto-GC was disabled. Having Py_Finalize() run GC even when it has been disabled seems wrong to me. Originally, cyclic GC was supposed to be optional. Back then, most programs did not leak cycles. I would vote for

Re: [Python-Dev] Adding Type[C] to PEP 484

Right. I still have no good intuition for what Type[BasicUser, ProUser] would mean so I think you should be required to use the Union, which is clear. Type[] should only allow one parameter. Most real uses of Type[] use a type variable anyway. I really recommend that you read through

Re: [Python-Dev] Adding Type[C] to PEP 484

On 14 May 2016 at 13:28, Guido van Rossum wrote: > On Sat, May 14, 2016 at 11:47 AM, Peter Ludemann > wrote: > >> I think that Type[C,D] would mean Union[Type[C], Type[D]], but I'm not >> sure ... I should probably talk to a typing expert about this.

Re: [Python-Dev] file system path protocol PEP

Greg Ewing writes: > Paul Moore wrote: > > On 13 May 2016 at 17:57, Ethan Furman wrote: > > > >>1) What is a wallet garden? > > > > I assumed he meant "walled garden" > > Works either way -- you'd want a wall around your wallet > garden to stop people stealing your

Re: [Python-Dev] Speeding up CPython 5-10%

2016-02-01 17:54 GMT+01:00 Yury Selivanov : > Thanks for bringing this up! > > IIRC wpython was about using "fat" bytecodes, i.e. using 64bits per > bytecode instead of 8. No, it used 16, 32, and 48-bit per opcode (1, 2, or 3 16-bit words). > That allows to minimize

Re: [Python-Dev] Wordcode: new regular bytecode using 16-bit units

2016-04-13 23:23 GMT+02:00 Victor Stinner : > Hopefully, I don't expect 32-bit parameters in the wild, only 24-bit > parameter for function with annotation. > I never found 32-bit parameters, and not even 24-bit ones. I think that their usage is as rare as all planets

Re: [Python-Dev] Wordcode: new regular bytecode using 16-bit units

2016-04-13 18:24 GMT+02:00 Victor Stinner : > Demur Rumed proposes a different change to use a regular bytecode > using 16-bit units: an instruction has always one 8-bit argument, it's > zero if the instruction doesn't have an argument: > >

Re: [Python-Dev] Wordcode v2

2016-02-17 12:04 GMT+01:00 Antoine Pitrou : > Demur Rumed gmail.com> writes: > > I've personally benchmarked this fork with positive results. > > I'm skeptical of claims like this. What did you benchmark exactly, and with > which results? > I don't think changing the opcode

Re: [Python-Dev] Wordcode v2

2016-02-15 8:14 GMT+01:00 Andrew Barnert via Python-Dev < python-dev@python.org>: > Despite the name (and inspiration), my fork has very little to do with > WPython. I'm just focused on simpler (hopefully = faster) fetch code; he > started with that, but ended up going the exact opposite

Re: [Python-Dev] Wordcode v2

2016-02-15 1:20 GMT+01:00 Demur Rumed : > Saw recent discussion: > https://mail.python.org/pipermail/python-dev/2016-February/143013.html > > I remember trying WPython; it was fast. Unfortunately it feels it came at > the wrong time when development was invested in getting

Re: [Python-Dev] file system path protocol PEP

On Fri, May 13, 2016 at 7:43 PM, Chris Angelico wrote: [...] > "Check" accepts subclasses; "CheckExact" doesn't (it's like "type(x) > is str"). The question is, which one SHOULD be being done? Indeed it should do "Check", so that path libraries that do inherit from str will

Re: [Python-Dev] Speeding up CPython 5-10%

2016-02-02 10:28 GMT+01:00 Victor Stinner : > 2016-01-27 19:25 GMT+01:00 Yury Selivanov : > > tl;dr The summary is that I have a patch that improves CPython > performance > > up to 5-10% on macro benchmarks. Benchmarks results on Macbook Pro/Mac