Skip to content

Conversation

@ZeroIntensity
Copy link
Member

@ZeroIntensity ZeroIntensity commented Oct 13, 2025

  • Change is either:
    • To a Draft PEP
    • To an Accepted or Final PEP, with Steering Council approval
    • To fix an editorial issue (markup, typo, link, header, etc)
  • PR title prefixed with PEP number (e.g. PEP 123: Summary of changes)

Rename PyInterpreterLock to PyInterpreterGuard, and also do a bunch of copyediting to improve the clarity of the proposal.


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

@ZeroIntensity
Copy link
Member Author

@vstinner Did you want a chance to review, or should I go ahead and merge this?

Copy link
Member

@vstinner vstinner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Just a few minor typos.

Co-authored-by: Victor Stinner <vstinner@python.org>
@ZeroIntensity
Copy link
Member Author

Thanks!

@ZeroIntensity ZeroIntensity enabled auto-merge (squash) October 14, 2025 11:21
@ZeroIntensity ZeroIntensity merged commit 8fc0771 into python:main Oct 14, 2025
5 checks passed
@ZeroIntensity ZeroIntensity deleted the pep-788-final-round branch October 17, 2025 02:49
zklaus pushed a commit to zklaus/peps that referenced this pull request Nov 3, 2025
* Rename to PyInterpreterGuard.

* Avoid locking terminology.

* Some clarity fixes.

---------

Co-authored-by: Victor Stinner <vstinner@python.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants