> That sounds like a horrible idea. The GIL should never be held during an
> I/O operation.
For a greenfield design, I agree that it would be perverse. But I thought we
were talking about affordances for transitions from code that was written
without consideration of multiple interpreters. In
On Fri, Mar 11, 2022 at 5:17 PM Victor Stinner wrote:
> It would be great to have the list of supported platforms per Python
> version!
>
I could see the table in PEP 11 being copied into the release PEPs.
>
> Maybe supporting new platforms and dropping support for a platform
> should be
On 12. 03. 22 2:45, Eric Snow wrote:
responses inline
I'll snip some discussion for a reason I'll get to later, and get right
to the third alternative:
[...]
"Special-casing immortal objects in tp_dealloc() for the relevant types
(but not int, due to frequency?)" sounds promising.
The
Hi,
Oh, the Steering Council accepted PEP 594 "Removing dead batteries
from the standard library"! I just saw the announcement on Discourse.
Congratulations Christian and Brett! This PEP, first proposed in 2019,
wasn't an easy one.
https://peps.python.org/pep-0594/
Gregory P. Smith's message on
