Skip to content

PEP 834: Maker syntax#4974

Open
JelleZijlstra wants to merge 14 commits into
python:mainfrom
JelleZijlstra:classbuilders
Open

PEP 834: Maker syntax#4974
JelleZijlstra wants to merge 14 commits into
python:mainfrom
JelleZijlstra:classbuilders

Conversation

@JelleZijlstra

@JelleZijlstra JelleZijlstra commented May 18, 2026 •
edited by hugovk
Loading

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
  • 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

@read-the-docs-community

read-the-docs-community Bot commented May 18, 2026 •
edited
Loading

Copy link
Copy Markdown

Documentation build overview

📚 pep-previews | 🛠️ Build #32812594 | 📁 Comparing b6e13f7 against latest (9cc461d)

  🔍 Preview build  

707 files changed · + 1 added · ± 706 modified

+ Added

± Modified

hugovk
hugovk reviewed May 19, 2026
View reviewed changes
Comment thread peps/pep-0834.rst Outdated
Comment thread peps/pep-0834.rst Outdated
JelleZijlstra and others added 3 commits May 19, 2026 05:30
@JelleZijlstra @hugovk
Apply suggestions from code review
ca9d990 
Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
@JelleZijlstra
makers
02904d7
@JelleZijlstra
make
bb922ad
@JelleZijlstra JelleZijlstra changed the title PEP 834: Class Builders PEP 834: Maker syntax May 22, 2026
@JelleZijlstra JelleZijlstra marked this pull request as ready for review May 22, 2026 15:15
@JelleZijlstra JelleZijlstra requested a review from a team as a code owner May 22, 2026 15:15
hugovk
hugovk reviewed Jun 12, 2026
View reviewed changes

@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.

Please add yourself to the CODEOWNERS file. I've also added the checklist to the description, please check off as necessary in case there's something else.

@brianschubert brianschubert added the new-pep A new draft PEP submitted for initial review label Jun 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@hugovk hugovk hugovk left review comments

Assignees

No one assigned

Labels

new-pep A new draft PEP submitted for initial review

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@JelleZijlstra @hugovk @brianschubert