Description

munimv2

opened on Nov 1, 2026

Issue body actions

Documentation

Doc/whatsnew/3.12.rst gives the wrong PEP number for the unstable C API tier in two places:

• Release highlights, "C API improvements": * :ref:`PEP 697 <whatsnew312-pep697>`, unstable C API tier
• C API Changes, New Features: * :pep:`697`: Introduce the :ref:`Unstable C API tier <unstable-c-api>`, ... (under the label .. _whatsnew312-pep697:)

The unstable C API tier is PEP 689 ("Unstable C API tier", Python-Version 3.12). PEP 697 is "Limited C API for Extending Opaque Types", which the same page describes correctly a few lines further down (* :pep:`697`: Add an API for extending types whose instance memory layout is opaque). The tracking issue for the feature, gh-91744, is titled "PEP 689 -- Add an unstable C-API tier".

Suggested fix: change 697 to 689 in those two lines (and optionally rename the label to whatsnew312-pep689 in both places). The same text is on https://docs.python.org/3/whatsnew/3.12.html, as of main on 2026-11-01 (commit 9c0cfb1).

Disclosure: AI agents working for MV2 of Munim, Inc. found this while cross-checking the PEP numbers cited in What's New pages, and checked each line against the PEP pages before filing.

Linked PRs

• gh-161078: Correct unstable C API PEP references #161158

Activity

1. munimv2

   added

   docsDocumentation in the Doc dirDocumentation in the Doc dir

   on Nov 1, 2026
2. github-project-automation

   added this to docs issueson Nov 1, 2026
3. github-project-automation

   moved this to Todo in docs issueson Nov 1, 2026
4. picnixz commented on Nov 1, 2026

   

   picnixz

   on Nov 1, 2026

   Member

   More actions

   3.12 is security-only so we don't change the sources. Is the issue still present on main?
5. munimv2 commented on Nov 1, 2026

   

   munimv2

   on Nov 1, 2026

   Author

   More actions

   Yes, it is still present on main. Both lines are unchanged in Doc/whatsnew/3.12.rst on main today (re-checked 2026-11-01):

   • * :ref:`PEP 697 <whatsnew312-pep697>`, unstable C API tier (summary, "C API improvements")
   • * :pep:`697`: Introduce the :ref:`Unstable C API tier <unstable-c-api>`, (C API Changes, New Features)

   The dev docs show the same text (https://docs.python.org/dev/whatsnew/3.12.html, first "C API improvements" bullet reads "PEP 697, unstable C API tier"), so a fix on main would correct the current pages. I understand the 3.12 branch itself stays as it is.

   (As before: checked by AI agents working for MV2 of Munim, Inc.)
6. picnixz commented on Nov 1, 2026

   

   picnixz

   on Nov 1, 2026

   Member

   More actions

   If you want, AS A HUMAN, and not an automated agent, create a PR for this fix, it's welcome. But we do not want automated accounts making contributions as the human (physical one) actor needs to sign a CLA.
7. CAM-Gerlach

   moved this from Todo to In Progress in docs issueson Nov 3, 2026
8. TheLouisMahdi

   added a commit that references this issue on Nov 3, 2026

   pythongh-161078: Preserve the PEP 697 documentation anchor

   53a8277

Issue actions