PEP 652 Accepted -- Maintaining the Stable ABI
Hi Petr, Thank you for submitting PEP 652 (Maintaining the Stable ABI). After evaluating the situation and discussing the PEP, the Steering Council is happy with the PEP and hereby accepts it. The Steering council thinks that this is a great step forward in order to have a clear definition of what goes into the Stable ABI and what guarantees the Python core team offers regarding the stable ABI while offering at the same time a plan to improve the maintenance and stability of the stable ABI. We would also like to see some improvements in the official documentation (not only on the devguide) regarding this topic and what guarantees do we offer (currently we only have a small section about this in https://docs.python.org/3/c-api/stable.html but there is a lot of information and clarifications in the PEP that we would like to be also in the documentation). Congratulations, Petr! With thanks from the whole Python Steering Council, Pablo Galindo Salgado
On 05. 04. 21 21:46, Pablo Galindo Salgado wrote:
Hi Petr,
Thank you for submitting PEP 652 (Maintaining the Stable ABI). After evaluating the situation and discussing the PEP, the Steering Council is happy with the PEP and hereby accepts it. The Steering council thinks that this is a great step forward in order to have a clear definition of what goes into the Stable ABI and what guarantees the Python core team offers regarding the stable ABI while offering at the same time a plan to improve the maintenance and stability of the stable ABI.
We would also like to see some improvements in the official documentation (not only on the devguide) regarding this topic and what guarantees do we offer (currently we only have a small section about this in https://docs.python.org/3/c-api/stable.html <https://docs.python.org/3/c-api/stable.html> but there is a lot of information and clarifications in the PEP that we would like to be also in the documentation).
Congratulations, Petr!
With thanks from the whole Python Steering Council, Pablo Galindo Salgado
Thanks to you and the CS for consideration! I'm definitely planning to update the documentation prose as well.
participants (2)
-
Pablo Galindo Salgado
-
Petr Viktorin