Skip to content

PEP 845: Leading-Dot Value Patterns - #5107

Merged
ethanfurman merged 7 commits into
python:mainfrom
tmke8:pep-845
Sep 17, 2026
Merged

ethanfurman merged 7 commits into
python:mainfrom
tmke8:pep-845

Conversation

@tmke8

@tmke8 tmke8 commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

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

@tmke8
tmke8 requested a review from a team as a code owner August 25, 2026 11:10
@read-the-docs-community

read-the-docs-community Bot commented Aug 25, 2026

Copy link
Copy Markdown

Comment thread peps/pep-0845.rst Outdated
Comment thread .github/CODEOWNERS Outdated
Co-authored-by: Marc Mueller <30130371+cdce8p@users.noreply.github.com>
Comment thread peps/pep-0845.rst Outdated
Comment thread peps/pep-0845.rst Outdated
Co-authored-by: Marc Mueller <30130371+cdce8p@users.noreply.github.com>
@hugovk

hugovk commented Aug 26, 2026

Copy link
Copy Markdown
Member
  • Core dev/PEP editor listed as Author or Sponsor, and formally confirmed their approval

@ethanfurman Please could you confirm your sponsorship?

@ethanfurman

Copy link
Copy Markdown
Member

Confirmed.

@brianschubert brianschubert added the new-pep A new draft PEP submitted for initial review label Sep 1, 2026

@hugovk hugovk left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

@ethanfurman Please could you also review and approve if you're happy with it?

Comment thread peps/pep-0845.rst Outdated
Comment thread peps/pep-0845.rst Outdated
Comment thread peps/pep-0845.rst Outdated
Comment thread peps/pep-0845.rst Outdated
Comment thread peps/pep-0845.rst Outdated
Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
Co-authored-by: Ethan Furman <ethan@stoneleaf.us>

@ethanfurman ethanfurman left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Looks good!

@ethanfurman
ethanfurman merged commit 738af4c into python:main Sep 17, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

new-pep A new draft PEP submitted for initial review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants