This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Title: doc: Update Defining New Types chapter according to PEP 253
Type: enhancement Stage:
Components: Documentation Versions: Python 3.10, Python 3.9
Status: open Resolution:
Dependencies: Superseder:
Assigned To: docs@python Nosy List: docs@python, mloskot
Priority: normal Keywords:

Created on 2012-06-07 17:25 by mloskot, last changed 2022-04-11 14:57 by admin.

Messages (2)
msg162480 - (view) Author: Mateusz Loskot (mloskot) * Date: 2012-06-07 17:25
The chapter '2. Defining New Types" in the Python 3.2 documentation [1] does not cover all important elements, especially in the subsection 2.1.4. Subclassing other types.

The accepted PEP 253 [2] provides much more detailed and thorough explanation for Python C API users willing to define and subclass new types, than the official manual.

I'd like to suggest update of the manual with information enclosed in the PEP 253. In fact, the PEP's sections like

* Preparing a type for subtyping
* Creating a subtype of a built-in type in C

could be copied with little editing, IMHO.

The PEP 253 really seems to be a must-read document for Python C API users.

msg162481 - (view) Author: Mateusz Loskot (mloskot) * Date: 2012-06-07 17:27
Similar request has been rejected in response to the Issue 621526 [1],
but I'm not proposing to include PEP into docs, but to update and improve docs with material discussed in accepted PEPs. 

Date User Action Args
2022-04-11 14:57:31adminsetgithub: 59234
2020-10-27 21:53:46iritkatrielsettitle: Update Defining New Types chapter according to PEP 253 -> doc: Update Defining New Types chapter according to PEP 253
versions: + Python 3.9, Python 3.10, - Python 3.2
2012-06-07 17:27:11mloskotsetmessages: + msg162481
2012-06-07 17:25:09mloskotcreate