From 050a751a2158a1ceba3868bdbd778b7717ed3764 Mon Sep 17 00:00:00 2001 From: Adam Turner <9087854+aa-turner@users.noreply.github.com> Date: Wed, 4 May 2022 00:42:35 +0200 Subject: [PATCH] Improve wording in Rationale > The current wording is in the rationale section, which is > setting out the justification for the proposal. To me, it > seems odd to phrase it "We need because > requires , but we don't guarantee requirement. > > My suggested rephrasing more explicity spells out that we > want to support properly, there is a reason the > current state doesn't work (no guarantees at an API level > of stability), and hence is needed that provides > those guarantees. - https://github.com/python/peps/pull/2559#discussion_r860177857 --- pep-0689.rst | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/pep-0689.rst b/pep-0689.rst index 0513ddcfd219..707923ffa9f9 100644 --- a/pep-0689.rst +++ b/pep-0689.rst @@ -29,9 +29,12 @@ The Python C-API is currently divided into `three tiers `, and requires deprecation warnings before changes - Private (internal) API, which can change at any time. -We need a tier between Public and Private to accommodate tools like -advanced debuggers and JIT compilers, which need access to CPython -internals but assume the C-API they use does not change in patch releases. +Tools requring access to CPython internals (e.g. advanced +debuggers and JIT compilers) are often built for minor series releases +of CPython, and assume that the C-API interals used do not change +in patch releases. To support these tools, we need a tier between the +Public and Private C-API, with guarantees on stability throughout +the minor-series release. Setting Stability Expectations