New submission from Antoine Pitrou pit...@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: d...@python
components: Documentation
messages: 117984
nosy: d...@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 rep...@bugs.python.org
http://bugs.python.org/issue10024
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
