Skip to content

Conversation

@voznesenskym
Copy link

@voznesenskym voznesenskym commented Nov 1, 2025

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
  • [TBD] 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
    • Rationale
    • Specification
    • Backwards Compatibility
    • Security Implications
    • How to Teach This
    • Reference Implementation
    • Rejected Ideas
    • Open Issues
  • 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

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

@voznesenskym voznesenskym requested a review from a team as a code owner November 1, 2025 01:19
@python-cla-bot
Copy link

python-cla-bot bot commented Nov 1, 2025

All commit authors signed the Contributor License Agreement.

CLA signed

@voznesenskym voznesenskym changed the title Voznesenskym pep 812 PEP 812 - Immutable variables with const keyword Nov 1, 2025
@Mariatta
Copy link
Member

Mariatta commented Nov 1, 2025

Have this been discussed in our Discourse Forum, and do you have a PEP sponsor? If not, please start the discussion there first.

@hugovk hugovk changed the title PEP 812 - Immutable variables with const keyword PEP 9999: Immutable variables with const keyword Nov 1, 2025
@hugovk
Copy link
Member

hugovk commented Nov 1, 2025

Please do as Mariatta suggested, and review PEP 1's Start with an idea for Python section.

See also https://discuss.python.org/t/why-not-a-const-keyword/86067 and the 7 linked threads.

@hugovk hugovk closed this Nov 1, 2025
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.

3 participants