PEP 838: Move to standards track

[konstin]

PEP 838 affects the stdlib venv module, so it goes into the standards track instead of the packaging track.

• Change is either:
  • To a Draft PEP
  • To an Accepted or Final PEP, with Steering Council approval
  • To fix an editorial issue (markup, typo, link, header, etc)
• PR title prefixed with PEP number (e.g. PEP 123: Summary of changes)

[AlexWaygood]

To me this fits in better as a packaging PEP, since the only part of the stdlib that it touches is a very-much packaging-related part of the stdlib (the venv module), and since it is proposing a standard that we are asking external packaging tools that write pyvenv.cfg files (uv, virtualenv) to comply with as well as the stdlib venv module.

But I don't have a particularly strong opinion, and have very little experience on packaging PEPs; very happy to defer to @ncoghlan and @pfmoore :-)

[read-the-docs-community]

Documentation build overview

📚 pep-previews | 🛠️ Build #33691585 | 📁 Comparing 90e97eb against latest (a4b453d)

🔍 Preview build

3 files changed

±pep-0764/index.html
±pep-0838/index.html
±topic/packaging/index.html

[AlexWaygood]

I hear this has been discussed with @warsaw as well, so I'll go ahead and land this -- thanks!