Skip to content

Commit a600918

Browse files
authored
PEP 733: Add Post-History (#3518)
1 parent 02da28b commit a600918

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

peps/pep-0733.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -30,8 +30,8 @@ Author: Erlend Egeberg Aasland <[email protected]>,
3030
Jelle Zijlstra <[email protected]>,
3131
Status: Draft
3232
Type: Informational
33-
Content-Type: text/x-rst
3433
Created: 16-Oct-2023
34+
Post-History: `01-Nov-2023 <https://discuss.python.org/t/pep-733-an-evaluation-of-python-s-public-c-api/37618>`__
3535

3636

3737
Abstract
@@ -65,7 +65,7 @@ conventions changed, and new usage patterns have emerged, such as bindings
6565
to languages other than C/C++. In the next few years, new developments
6666
are expected to further test the C API, such as the removal of the GIL
6767
and the development of a JIT compiler. However, this growth was not
68-
supported by clearly documented guidelines, resulting in inconsitent
68+
supported by clearly documented guidelines, resulting in inconsistent
6969
approaches to API design in different subsystems of CPython. In addition,
7070
CPython is no longer the only implementation of Python, and some of the
7171
design decisions made when it was, are difficult for alternative

0 commit comments

Comments
 (0)