PEP 788: Reimagining native threads

[ZeroIntensity]

cc @vstinner

This is a PEPified version of this thread, which stemmed off of this other thread.

Basic requirements (all PEP Types)

• Read and followed PEP 1 & PEP 12
• File created from the latest PEP template
• PEP has next available number, & set in filename (pep-NNNN.rst), PR title (PEP 123: <Title of PEP>) and PEP header
• Title clearly, accurately and concisely describes the content in 79 characters or less
• Core dev/PEP editor listed as Author or Sponsor, and formally confirmed their approval
• Author, Status (Draft), Type and Created headers filled out correctly
• PEP-Delegate, Topic, Requires and Replaces headers completed if appropriate
• Required sections included
  • Abstract (first section)
  • Copyright (last section; exact wording from template required)
• Code is well-formatted (PEP 7/PEP 8) and is in code blocks, with the right lexer names if non-Python
• PEP builds with no warnings, pre-commit checks pass and content displays as intended in the rendered HTML
• Authors/sponsor added to .github/CODEOWNERS for the PEP

Standards Track requirements

• PEP topic discussed in a suitable venue with general agreement that a PEP is appropriate
• Suggested sections included (unless not applicable)
  • Motivation
  • Rationale
  • Specification
  • Backwards Compatibility
  • Security Implications
  • How to Teach This
  • Reference Implementation
  • Rejected Ideas
  • Open Issues
• Python-Version set to valid (pre-beta) future Python version, if relevant
• Any project stated in the PEP as supporting/endorsing/benefiting from the PEP formally confirmed such
• Right before or after initial merging, PEP discussion thread created and linked to in Discussions-To and Post-History

---

📚 Documentation preview 📚: https://pep-previews--4385.org.readthedocs.build/pep-0788/

[AA-Turner]

Several editorial suggestions. Thanks!

A

[ZeroIntensity]

I've realized a minor use-case that the proposal doesn't cover. I need make a few additions, so please refrain from merging for now.

[ZeroIntensity]

Ok, reference implementation and PEP updated. Sorry about the extra hassle there! @hugovk, this is ready otherwise. Would you like to give PyInterpreterState_Lookup a once-over?

[AA-Turner]

@ZeroIntensity ready to merge?

A

[ZeroIntensity]

Yup!

[hugovk]

@ZeroIntensity Congratulations on your first PEP! Please open the discussions thread, then open a quick PR to add it to Discussions-To and Post-History. Thanks!

[AA-Turner]

When you've created the discuss.p.o thread, please make a follow up PR here to add it to Discussions-To and Post-History.

A