[docs] [issue10024] Outdated advice in C-API tutorial?
Antoine Pitrou
report at bugs.python.org
Mon Oct 4 23:45:52 CEST 2010
New submission from Antoine Pitrou <pitrou at free.fr>:
In http://docs.python.org/dev/extending/newtypes.html, you can read:
“To enable object creation, we have to provide a tp_new implementation. In this case, we can just use the default implementation provided by the API function PyType_GenericNew(). We’d like to just assign this to the tp_new slot, but we can’t, for portability sake, On some platforms or compilers, we can’t statically initialize a structure member with a function defined in another C module, so, instead, we’ll assign the tp_new slot in the module initialization function just before calling PyType_Ready()”
But the thing is, we ourselves (CPython) do exactly what is discouraged here, both in built-in types and dynamically loaded extensions.
So is this piece of advice still necessary?
----------
assignee: docs at python
components: Documentation
messages: 117984
nosy: docs at python, loewis, pitrou
priority: normal
severity: normal
status: open
title: Outdated advice in C-API tutorial?
type: resource usage
versions: Python 2.7, Python 3.1, Python 3.2
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue10024>
_______________________________________
More information about the docs
mailing list