[issue15029] Update Defining New Types chapter according to PEP 253

2012-06-07 Thread Mateusz Loskot

New submission from Mateusz Loskot mate...@loskot.net:

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/

--
assignee: docs@python
components: Documentation
messages: 162480
nosy: docs@python, mloskot
priority: normal
severity: normal
status: open
title: Update Defining New Types chapter according to PEP 253
type: enhancement
versions: Python 3.2

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15029
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue15029] Update Defining New Types chapter according to PEP 253

2012-06-07 Thread Mateusz Loskot

Mateusz Loskot mate...@loskot.net added the comment:

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. 

[1] http://bugs.python.org/issue621526

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15029
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com