Message 207927 - Python tracker

➜

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	ncoghlan
Recipients	docs@python, ncoghlan
Date	2014-01-12.06:25:10
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1389507911.71.0.277009038491.issue20224@psf.upfronthosting.co.za>
In-reply-to

Content
The main C API docs don't clearly explain how to define new types, so people almost always cargo cult an existing legacy type definition instead (I know I do). The extending and embedding docs have a guide (http://docs.python.org/3/extending/newtypes.html), but that describes the old legacy method based on static type declarations. New code should instead use the dynamic mechanism defined in PEP 384 (http://www.python.org/dev/peps/pep-0384/#type-objects). See also http://docs.python.org/3/c-api/type.html#PyType_FromSpec Note that PyType_Spec isn't defined in the C API docs at all.

The main C API docs don't clearly explain how to define new types, so people almost always cargo cult an existing legacy type definition instead (I know I do).

The extending and embedding docs have a guide (http://docs.python.org/3/extending/newtypes.html), but that describes the old legacy method based on static type declarations. New code should instead use the dynamic mechanism defined in PEP 384 (http://www.python.org/dev/peps/pep-0384/#type-objects).

See also http://docs.python.org/3/c-api/type.html#PyType_FromSpec

Note that PyType_Spec isn't defined in the C API docs *at all*.

History
Date	User	Action	Args
2014-01-12 06:25:11	ncoghlan	set	recipients: + ncoghlan, docs@python
2014-01-12 06:25:11	ncoghlan	set	messageid: <1389507911.71.0.277009038491.issue20224@psf.upfronthosting.co.za>
2014-01-12 06:25:11	ncoghlan	link	issue20224 messages
2014-01-12 06:25:10	ncoghlan	create