PEP 624
E908120
PEP 624 is a Python Enhancement Proposal that specifies the removal of the Py_UNICODE encoder APIs from the CPython C API to streamline and modernize Unicode handling in Python.
All labels observed (1)
| Label | Occurrences |
|---|---|
| PEP 624 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T10763899 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PEP 624 Context triple: [Python 3.10, implementsPEP, PEP 624]
-
A.
PEP 622
PEP 622 is a Python Enhancement Proposal that introduced the design for structural pattern matching syntax later adopted in Python 3.10.
-
B.
PEP 634
PEP 634 is the Python Enhancement Proposal that formally specifies the semantics of structural pattern matching introduced in Python 3.10.
-
C.
PEP 614
PEP 614 is a Python Enhancement Proposal that relaxes the grammar restrictions on decorator syntax, allowing more flexible and expressive decorator expressions in Python.
-
D.
PEP 604
PEP 604 is a Python Enhancement Proposal that introduced the modern, concise syntax for expressing type unions (using the `|` operator) in Python’s type hints.
-
E.
PEP 636
PEP 636 is a Python Enhancement Proposal that serves as a tutorial-style guide to the structural pattern matching feature introduced in Python 3.10.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: PEP 624 Target entity description: PEP 624 is a Python Enhancement Proposal that specifies the removal of the Py_UNICODE encoder APIs from the CPython C API to streamline and modernize Unicode handling in Python.
-
A.
PEP 622
PEP 622 is a Python Enhancement Proposal that introduced the design for structural pattern matching syntax later adopted in Python 3.10.
-
B.
PEP 634
PEP 634 is the Python Enhancement Proposal that formally specifies the semantics of structural pattern matching introduced in Python 3.10.
-
C.
PEP 614
PEP 614 is a Python Enhancement Proposal that relaxes the grammar restrictions on decorator syntax, allowing more flexible and expressive decorator expressions in Python.
-
D.
PEP 604
PEP 604 is a Python Enhancement Proposal that introduced the modern, concise syntax for expressing type unions (using the `|` operator) in Python’s type hints.
-
E.
PEP 636
PEP 636 is a Python Enhancement Proposal that serves as a tutorial-style guide to the structural pattern matching feature introduced in Python 3.10.
- F. None of above. chosen
Statements (50)
| Predicate | Object |
|---|---|
| instanceOf | Python Enhancement Proposal ⓘ |
| affects | C extensions using Py_UNICODE encoder APIs ⓘ |
| author | Victor Stinner ⓘ |
| backwardsCompatibility | requires changes in third-party C extensions ⓘ |
| created | 2020-02-24 ⓘ |
| discussedOn | python-dev mailing list ⓘ |
| focusesOn |
CPython C API
ⓘ
linked to:
C API
Unicode handling ⓘ |
| language | Python ⓘ |
| motivation |
remove legacy Py_UNICODE based APIs
ⓘ
streamline and modernize Unicode handling in the CPython C API ⓘ |
| number | 624 ⓘ |
| partOf | CPython C API modernization efforts ⓘ |
| pepIndexUrl | https://peps.python.org/pep-0624/ ⓘ |
| recommends |
using PyUnicode_New and PEP 393 flexible string representation
ⓘ
using bytes and standard codec APIs instead of Py_UNICODE encoders ⓘ |
| relatedTo |
PEP 393
ⓘ
PEP 623 ⓘ |
| repository | https://github.com/python/peps ⓘ |
| specifiesRemovalOf |
PyUnicode_Encode
ⓘ
PyUnicode_EncodeASCII ⓘ PyUnicode_EncodeCharmap ⓘ PyUnicode_EncodeCharmapStateful ⓘ PyUnicode_EncodeCodePage ⓘ PyUnicode_EncodeCodePageStateful ⓘ
linked to:
PyUnicode_EncodeCodePage
PyUnicode_EncodeDecimal ⓘ PyUnicode_EncodeFSDefault ⓘ PyUnicode_EncodeFSDefaultStateful ⓘ
linked to:
PyUnicode_EncodeFSDefault
PyUnicode_EncodeLatin1 ⓘ PyUnicode_EncodeLocale ⓘ PyUnicode_EncodeLocaleStateful ⓘ PyUnicode_EncodeMBCS ⓘ PyUnicode_EncodeMBCSStateful ⓘ
linked to:
PyUnicode_EncodeMBCS
PyUnicode_EncodeRawUnicodeEscape ⓘ PyUnicode_EncodeUTF16 ⓘ PyUnicode_EncodeUTF16Stateful ⓘ PyUnicode_EncodeUTF32 ⓘ PyUnicode_EncodeUTF32Stateful ⓘ
linked to:
PyUnicode_EncodeUTF32
PyUnicode_EncodeUTF7 ⓘ
linked to:
UTF-7
PyUnicode_EncodeUTF7Stateful ⓘ PyUnicode_EncodeUTF8 ⓘ PyUnicode_EncodeUTF8Stateful ⓘ PyUnicode_EncodeUnicodeEscape ⓘ PyUnicode_TransformDecimalToASCII ⓘ PyUnicode_TranslateCharmap ⓘ Py_UNICODE encoder APIs ⓘ |
| status | Final ⓘ |
| targetImplementation |
CPython
ⓘ
linked to:
Python reference implementation (CPython)
|
| title | Remove Py_UNICODE encoder APIs ⓘ |
| type | Standards Track ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: PEP 624 Description of subject: PEP 624 is a Python Enhancement Proposal that specifies the removal of the Py_UNICODE encoder APIs from the CPython C API to streamline and modernize Unicode handling in Python.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.