Skip to content

PEP 848: Incremental Generational GC - #5140

Merged
markshannon merged 2 commits into
python:mainfrom
markshannon:incremental-gc-pep
Sep 25, 2026
Merged

markshannon merged 2 commits into
python:mainfrom
markshannon:incremental-gc-pep

Conversation

@markshannon

@markshannon markshannon commented Sep 24, 2026 •

Copy link
Copy Markdown
Member

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
    • Tip: find the next available number with pepotron — run uvx pepotron next (or pipx install pepotron then pep next)
  • 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
    • Specification
    • Rationale
    • Backwards Compatibility
    • Security Implications
    • How to Teach This
    • Reference Implementation
    • Rejected Ideas
    • Open Issues
    • Acknowledgements
    • Footnotes
    • Change History
  • 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

@markshannon
markshannon requested a review from a team as a code owner September 24, 2026 15:01
@read-the-docs-community

read-the-docs-community Bot commented Sep 24, 2026 •

Copy link
Copy Markdown

Comment thread peps/pep-0848.rst
Comment thread peps/pep-0848.rst Outdated
Comment thread peps/pep-0848.rst Outdated
Comment thread peps/pep-0848.rst Outdated
Comment thread peps/pep-0848.rst
Comment thread peps/pep-0848.rst Outdated
Comment thread peps/pep-0848.rst
Comment thread peps/pep-0848.rst
Comment thread peps/pep-0848.rst Outdated
Comment thread peps/pep-0848.rst
StanFromIreland

This comment was marked as duplicate.

@markshannon

Copy link
Copy Markdown
Member Author

@StanFromIreland thanks for the review. All resolved.

@markshannon
markshannon merged commit 30d6574 into python:main Sep 25, 2026
5 checks passed
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