iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

PEP 733: Add Post-History (#3518)

This commit is contained in:
Hugo van Kemenade 2023-11-01 16:42:24 +02:00 committed by GitHub
parent 02da28b2bd
commit a60091889e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
peps/pep-0733.rst
View File

@ -30,8 +30,8 @@ Author: Erlend Egeberg Aasland <erlend@python.org>,
Jelle Zijlstra <jelle.zijlstra@gmail.com>,
Status: Draft
Type: Informational
Content-Type: text/x-rst
Created: 16-Oct-2023
Post-History: `01-Nov-2023 <https://discuss.python.org/t/pep-733-an-evaluation-of-python-s-public-c-api/37618>`__
Abstract
@ -65,7 +65,7 @@ conventions changed, and new usage patterns have emerged, such as bindings
to languages other than C/C++. In the next few years, new developments
are expected to further test the C API, such as the removal of the GIL
and the development of a JIT compiler. However, this growth was not
supported by clearly documented guidelines, resulting in inconsitent
supported by clearly documented guidelines, resulting in inconsistent
approaches to API design in different subsystems of CPython. In addition,
CPython is no longer the only implementation of Python, and some of the
design decisions made when it was, are difficult for alternative