PEP 689: Tweak a policy, add canonical-doc and Mark as Final (GH-3123)

This commit is contained in:
Petr Viktorin 2023-05-09 11:44:32 +02:00 committed by GitHub
parent 5cea9b5d29
commit 254925bed6
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 7 additions and 3 deletions

View File

@ -49,6 +49,7 @@ exclude_patterns = [
intersphinx_mapping = { intersphinx_mapping = {
'python': ('https://docs.python.org/3/', None), 'python': ('https://docs.python.org/3/', None),
'packaging': ('https://packaging.python.org/en/latest/', None), 'packaging': ('https://packaging.python.org/en/latest/', None),
'devguide': ('https://devguide.python.org/', None),
'py3.11': ('https://docs.python.org/3.11/', None), 'py3.11': ('https://docs.python.org/3.11/', None),
'py3.12': ('https://docs.python.org/3.12/', None), 'py3.12': ('https://docs.python.org/3.12/', None),
} }

View File

@ -2,7 +2,7 @@ PEP: 689
Title: Unstable C API tier Title: Unstable C API tier
Author: Petr Viktorin <encukou@gmail.com> Author: Petr Viktorin <encukou@gmail.com>
Discussions-To: https://discuss.python.org/t/pep-689-unstable-c-api-tier/20452 Discussions-To: https://discuss.python.org/t/pep-689-unstable-c-api-tier/20452
Status: Accepted Status: Final
Type: Standards Track Type: Standards Track
Content-Type: text/x-rst Content-Type: text/x-rst
Requires: 523 Requires: 523
@ -13,6 +13,10 @@ Post-History: `27-Apr-2022 <https://mail.python.org/archives/list/python-dev@pyt
`27-Oct-2022 <https://discuss.python.org/t/pep-689-unstable-c-api-tier/20452>`__, `27-Oct-2022 <https://discuss.python.org/t/pep-689-unstable-c-api-tier/20452>`__,
Resolution: https://discuss.python.org/t/pep-689-unstable-c-api-tier/20452/13 Resolution: https://discuss.python.org/t/pep-689-unstable-c-api-tier/20452/13
.. canonical-doc:: :ref:`devguide:c-api`
User-facing documentation is at :ref:`py3.12:unstable-c-api`.
Abstract Abstract
======== ========
@ -152,8 +156,7 @@ Several rules for dealing with the unstable tier will be introduced:
- To move an API from the unstable tier to the public tier, it should be - To move an API from the unstable tier to the public tier, it should be
exposed without the ``PyUnstable_*`` prefix. exposed without the ``PyUnstable_*`` prefix.
The old name should remain available until the first incompatible change The old name should remain available until the API is deprecated or removed.
is made or the API is removed.
- Adding new unstable API *for existing features* is allowed even after - Adding new unstable API *for existing features* is allowed even after
Beta feature freeze, up until the first Release Candidate. Beta feature freeze, up until the first Release Candidate.