PEP 838: Adding python-version to pyvenv.cfg

[konsti-openai]

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)
    -> Picked the next id after PEP 837: Extensible JSON serialization #5031
• 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

Packaging track, but close enough

• [n/a] 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
  • [n/a] Security Implications
  • How to Teach This
  • Reference Implementation
  • [n/a] Rejected Ideas
  • [n/a] Open Issues
  • [n/a] 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

[python-cla-bot]

All commit authors signed the Contributor License Agreement.

[read-the-docs-community]

Documentation build overview

📚 pep-previews | 🛠️ Build #33617464 | 📁 Comparing 312bb9e against latest (8618d76)

🔍 Preview build

7 files changed · + 2 added · ± 5 modified

+Added

• pep-0838/index.html
• pep-0840/index.html

±Modified

• index.html
• numerical/index.html
• pep-0000/index.html
• pep-0764/index.html
• topic/packaging/index.html

[ncoghlan]

While it has packaging implications, this is a regular Standards track PEP for the venv module and interpreter startup, not a Packaging PEP. Accordingly, it also isn't covered by Paul's standing delegation.

[ncoghlan]

Checking PEP 405 itself brought my attention to #2636, which misclassified PEP 405, and that is presumably the origin of this misclassification.

I was wearing my "interpreter startup configuration" core developer hat for that particular PEP rather than the packaging interoperability role that I acquired later.

[konstin]

I changed the track in #5053