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.

Author mloskot
Recipients docs@python, mloskot
Date 2012-06-07.17:25:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1339089909.82.0.778815916296.issue15029@psf.upfronthosting.co.za>
In-reply-to
Content
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.

[1] http://docs.python.org/release/3.2.2/extending/newtypes.html
[2] http://www.python.org/dev/peps/pep-0253/
History
Date User Action Args
2012-06-07 17:25:09mloskotsetrecipients: + mloskot, docs@python
2012-06-07 17:25:09mloskotsetmessageid: <1339089909.82.0.778815916296.issue15029@psf.upfronthosting.co.za>
2012-06-07 17:25:09mloskotlinkissue15029 messages
2012-06-07 17:25:08mloskotcreate