From 43028f180d7de4e0b65b9538424b4c2b856aaa9f Mon Sep 17 00:00:00 2001 From: Victor Stinner Date: Tue, 22 Feb 2022 13:37:51 +0100 Subject: [PATCH] PEP 670: Complete History --- pep-0670.rst | 27 +++++++++++++++++++++++---- 1 file changed, 23 insertions(+), 4 deletions(-) diff --git a/pep-0670.rst b/pep-0670.rst index bd331f223..7f8e3601e 100644 --- a/pep-0670.rst +++ b/pep-0670.rst @@ -581,6 +581,10 @@ functions. Post History ============ +* python-dev: `Steering Council reply to PEP 670 -- Convert macros to + functions in the Python C API + `_ + (February 2022) * python-dev: `PEP 670: Convert macros to functions in the Python C API `_ (October 2021) @@ -589,9 +593,10 @@ Post History References ========== + * `bpo-45490 `_: - [meta][C API] Avoid C macro pitfalls and usage of static inline - functions (October 2021). + [C API] PEP 670: Convert macros to functions in the Python C API + (October 2021). * `What to do with unsafe macros `_ (March 2021). @@ -603,8 +608,22 @@ References Version History =============== -* Version 2: No longer remove return values; remove argument casting - from the limited C API. +* Version 2: + + * Stricter policy on not changing argument types and return type. + * Better explain why pointer arguments require a cast to not emit new + compiler warnings. + * Macros which can be used as l-values are no longer modified by the + PEP. + * Macros having multiple return types are no longer modified by the + PEP. + * Limited C API version 3.11 no longer casts pointer arguments. + * No longer remove return values of macros "which should not have a + return value". + * Add "Macros converted to functions since Python 3.8" section. + * Add "Benchmark comparing macros and static inline functions" + section. + * Version 1: First public version