[Python-Dev] Re: Python release announcement format

On Tue, Dec 14, 2021 at 9:06 AM Yann Droneaud wrote: > Hi, > > I'm not familiar with the Python release process, but looking at the latest > release > https://www.python.org/downloads/release/python-3101/ > > we can see MD5 is still used ... which doesn't sound right in 2021 ... > especially sin

[Python-Dev] Re: my plans for subinterpreters (and a per-interpreter GIL)

Whoops, never mind, I see that you started the "immortal objects" thread to discuss this. On Tue, Dec 14, 2021 at 4:54 PM Nathaniel Smith wrote: > > How did you end up solving the issue where Py_None is a static global > that's exposed as part of the stable C ABI? > > On Tue, Dec 14, 2021 at 9:13

[Python-Dev] Re: my plans for subinterpreters (and a per-interpreter GIL)

How did you end up solving the issue where Py_None is a static global that's exposed as part of the stable C ABI? On Tue, Dec 14, 2021 at 9:13 AM Eric Snow wrote: > > Hi all, > > I'm still hoping to land a per-interpreter GIL for 3.11. There is > still a decent amount of work to be done but litt

[Python-Dev] Re: "immortal" objects and how they would help per-interpreter GIL

On Tue, Dec 14, 2021 at 4:09 PM Brett Cannon wrote: > There's also the concern of memory usage if these immortal objects are never > collected. > > But which objects are immortal? You only listed None, True, and False. > Otherwise assume/remember I'm management and provide a list and/or link of

[Python-Dev] Re: subinterpreters and their possible impact on large extension projects

Yeah, no (mutable) global state at the C level. It would also be good to implement multi-phase init (PEP 489), but I don't expect that to require much work itself. -eric On Tue, Dec 14, 2021 at 4:04 PM Brett Cannon wrote: > > > > On Tue, Dec 14, 2021 at 9:41 AM Eric Snow wrote: >> >> One of th

[Python-Dev] Re: Python release announcement format

On Tue, Dec 14, 2021 at 11:56:09AM +0100, Yann Droneaud wrote: > Hi, > > I'm not familiar with the Python release process, but looking at the latest > release > > https://www.python.org/downloads/release/python-3101/ > > we can see MD5 is still used ... which doesn't sound right in 2021 ... > e

[Python-Dev] Re: "immortal" objects and how they would help per-interpreter GIL

On Tue, Dec 14, 2021 at 10:23 AM Eric Snow wrote: > Most of the work toward interpreter isolation and a per-interpreter > GIL involves moving static global variables to _PyRuntimeState or > PyInterpreterState (or module state). Through the effort of quite a > few people, we've made good progress

[Python-Dev] Re: subinterpreters and their possible impact on large extension projects

On Tue, Dec 14, 2021 at 9:41 AM Eric Snow wrote: > One of the open questions relative to subinterpreters is: how to > reduce the amount of work required for extension modules to support > them? Thanks to Petr Viktorin for a lot of work he's done in this > area (e.g. PEP 489)! Extensions also ha

[Python-Dev] Re: Python release announcement format

On 14/12/2021 11.56, Yann Droneaud wrote: Hi, I'm not familiar with the Python release process, but looking at the latest release https://www.python.org/downloads/release/python-3101/ we can see MD5 is still used ... which doesn't sound right in 2021 ... especially since we proved it's possib

[Python-Dev] Re: [python-committers] Sad news from Zurich

Fredrik was a lovely man who was also essential to the development of Python as it is today. I'm sorry that I only met him once, and I will miss him greatly. Metta, Ivan -- Ivan Van Laningham God N Locomotive Works https://legacy.python.org/workshops/1998-11/proceedings/papers/laningham/laningha

[Python-Dev] Re: Should dataclasses add__set__ (and possibly __get __) descriptors ?

Oh certainly that's the approach I was intending, basically wanted to make an enum that shares the methods that the original class can do, but this is quite helpful, I've been testing this approach and seems to work very well despite only working with *args, thanks a lot for the reply and everyo

[Python-Dev] "immortal" objects and how they would help per-interpreter GIL

Most of the work toward interpreter isolation and a per-interpreter GIL involves moving static global variables to _PyRuntimeState or PyInterpreterState (or module state). Through the effort of quite a few people, we've made good progress. However, many globals still remain, with the majority bei

[Python-Dev] subinterpreters and their possible impact on large extension projects

One of the open questions relative to subinterpreters is: how to reduce the amount of work required for extension modules to support them? Thanks to Petr Viktorin for a lot of work he's done in this area (e.g. PEP 489)! Extensions also have the option to opt out of subinterpreter support. Howeve

[Python-Dev] my plans for subinterpreters (and a per-interpreter GIL)

Hi all, I'm still hoping to land a per-interpreter GIL for 3.11. There is still a decent amount of work to be done but little of it will require solving any big problems: * pull remaining static globals into _PyRuntimeState and PyInterpreterState * minor updates to PEP 554 * finish up the last c

[Python-Dev] Python release announcement format

Hi, I'm not familiar with the Python release process, but looking at the latest release https://www.python.org/downloads/release/python-3101/ we can see MD5 is still used ... which doesn't sound right in 2021 ... especially since we proved it's possible to build different .tar.gz that have the