delta/cpython-git.git/Include/cpython, branch main

gh-103763: Implement PEP 695 (#103764)

2023-05-16T03:36:23+00:00

This implements PEP 695, Type Parameter Syntax. It adds support for:

- Generic functions (def func[T](): ...)
- Generic classes (class X[T](): ...)
- Type aliases (type X = ...)
- New scoping when the new syntax is used within a class body
- Compiler and interpreter changes to support the new syntax and scoping rules 

Co-authored-by: Marc Mueller <30130371+cdce8p@users.noreply.github.com>
Co-authored-by: Eric Traut 
Co-authored-by: Larry Hastings 
Co-authored-by: Alex Waygood

gh-104341: Adjust tstate_must_exit() to Respect Interpreter Finalization (gh-104437)

2023-05-15T19:59:26+00:00

With the move to a per-interpreter GIL, this check slipped through the cracks.

GH-102181: Improve specialization stats for SEND (GH-102182)

2023-05-10T22:40:59+00:00

gh-104223: Fix issues with inheriting from buffer classes (#104227)

2023-05-08T16:52:41+00:00

Co-authored-by: Kumar Aditya <59607654+kumaraditya303@users.noreply.github.com>

gh-99113: Add PyInterpreterConfig.own_gil (gh-104204)

2023-05-05T21:59:20+00:00

We also add PyInterpreterState.ceval.own_gil to record if the interpreter actually has its own GIL.

Note that for now we don't actually respect own_gil; all interpreters still share the one GIL.  However, PyInterpreterState.ceval.own_gil does reflect PyInterpreterConfig.own_gil.  That lie is a temporary one that we will fix when the GIL really becomes per-interpreter.

GH-96803: Add three C-API functions to make _PyInterpreterFrame less opaque for users of PEP 523. (GH-96849)

2023-05-05T16:53:07+00:00

gh-103509: PEP 697 -- Limited C API for Extending Opaque Types (GH-103511)

2023-05-04T07:56:53+00:00


Co-authored-by: Oleg Iarygin 
Co-authored-by: Erlend E. Aasland

gh-104109: Expose Py_NewInterpreterFromConfig() in the Public C-API (gh-104110)

2023-05-03T03:40:00+00:00

We also expose PyInterpreterConfig. This is part of the PEP 684 (per-interpreter GIL) implementation.  We will add docs as soon as we can.

FYI, I'm adding the new config field for per-interpreter GIL in gh-99114.

gh-103743: Add PyUnstable_Object_GC_NewWithExtraData (GH-103744)

2023-05-02T11:38:46+00:00


Co-authored-by: Petr Viktorin 
Co-authored-by: Erlend E. Aasland

gh-101659: Isolate "obmalloc" State to Each Interpreter (gh-101660)

2023-04-24T23:23:57+00:00

This is strictly about moving the "obmalloc" runtime state from
`_PyRuntimeState` to `PyInterpreterState`.  Doing so improves isolation
between interpreters, specifically most of the memory (incl. objects)
allocated for each interpreter's use.  This is important for a
per-interpreter GIL, but such isolation is valuable even without it.

FWIW, a per-interpreter obmalloc is the proverbial
canary-in-the-coalmine when it comes to the isolation of objects between
interpreters.  Any object that leaks (unintentionally) to another
interpreter is highly likely to cause a crash (on debug builds at
least).  That's a useful thing to know, relative to interpreter
isolation.