Skip to content

Comments

PEP 826: Python 3.16 Release Schedule#4829

Merged
savannahostrowski merged 11 commits intopython:mainfrom
savannahostrowski:3.16-schedule
Feb 23, 2026
Merged

PEP 826: Python 3.16 Release Schedule#4829
savannahostrowski merged 11 commits intopython:mainfrom
savannahostrowski:3.16-schedule

Conversation

@savannahostrowski
Copy link
Member

@savannahostrowski savannahostrowski commented Feb 23, 2026

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

It is very early but I'm currently planning out travel for the year and so figured I'd open the draft of this now. Not totally sure on the timing for merging this but I'm sure @hugovk will let me know :D


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

@savannahostrowski savannahostrowski requested a review from a team as a code owner February 23, 2026 18:29
@savannahostrowski savannahostrowski added the new-pep A new draft PEP submitted for initial review label Feb 23, 2026
@savannahostrowski savannahostrowski changed the title PEP 823: Python 3.16 Release Schedule PEP 826: Python 3.16 Release Schedule Feb 23, 2026
hugovk

This comment was marked as resolved.

AA-Turner

This comment was marked as resolved.

Copy link
Member

@AA-Turner AA-Turner left a comment

Choose a reason for hiding this comment

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

Exciting!

A

Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
@savannahostrowski savannahostrowski merged commit f29099e into python:main Feb 23, 2026
5 checks passed

[metadata."3.16"]
pep = 826
status = ""
Copy link
Member

Choose a reason for hiding this comment

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

@AA-Turner What value should we have here? The docs build got an error:

ValueError: Saw invalid version status '', expected to be one of EOL, bugfix, end-of-life, feature, in development, pre-release, prerelease, security, security-fixes, stable.
(1 additional frame(s) were not displayed)
...
  File "build_docs.py", line 1018, in main
    return build_docs_with_lock(args, "build_docs_html_en.lock")
  File "build_docs.py", line 1169, in build_docs_with_lock
    return build_docs(args)
  File "build_docs.py", line 1179, in build_docs
    versions = parse_versions_from_peps_site(http)
  File "build_docs.py", line 1264, in parse_versions_from_peps_site
    return Versions.from_json(releases)
  File "build_docs.py", line 118, in from_json
    raise ValueError(msg)

Copy link
Member

Choose a reason for hiding this comment

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

oh this is my fault, sorry. really 'feature' isn't appropriate, i thought i had written the support code to handle the empty string.

I'll put up a fix after dinner (NYC time)

A

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.

4 participants