Repository navigation
Implement PEP 684: A Per-Interpreter GIL #99113
Copy link
Copy link
Closed
Labels
3.12only security fixesonly security fixesinterpreter-core(Objects, Python, Grammar, and Parser dirs)(Objects, Python, Grammar, and Parser dirs)topic-subinterpreterstype-featureA feature request or enhancementA feature request or enhancement
Description
Activity
- addedtype-featureA feature request or enhancementA feature request or enhancementinterpreter-core(Objects, Python, Grammar, and Parser dirs)(Objects, Python, Grammar, and Parser dirs)3.12only security fixesonly security fixes
on Nov 5, 2022 Docs updates:
- add docs for
Py_NewInterpreterFromConfig()andPyInterpreterConfig - gh-99113: A Per-Interpreter GIL! #99114 (comment)
- ...
- add docs for
- added a commit that references this issue
on May 5, 2023 - added 5 commits that reference this issue
on May 8, 2023 - added a commit that references this issue
on May 8, 2023 @ericsnowcurrently, do you still want to keep this open? IIRC, most of the follow-up work is tracked in separate issues.
Yeah, I think you're right.
Metadata
Metadata
Assignees
Labels
3.12only security fixesonly security fixesinterpreter-core(Objects, Python, Grammar, and Parser dirs)(Objects, Python, Grammar, and Parser dirs)topic-subinterpreterstype-featureA feature request or enhancementA feature request or enhancement
Projects
- StatusShow more project fieldsDone
While PEP 684 is not accepted yet (and could get rejected, of course), it would be helpful to have an issue against which I can start creating draft PRs for the implementation.
This issue isn't for all the prerequisite work for a per-interpreter GIL, rather just the implementation of what's actually specified in the PEP. The rest is happening separately.
(Also see my checklist: https://github.com/ericsnowcurrently/multi-core-python/wiki/0-The-Plan)