Changes by Mark Lawrence breamore...@yahoo.co.uk:
--
nosy: -BreamoreBoy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6128
___
___
Christian Aichinger added the comment:
I concur that this aspect of writing Python types in C/C++ needs better
documentation. For a new extension writer (like me), it is not obvious when
PyObject_GC_Track/PyObject_GC_UnTrack must be called or not. Similarly, it is
not clear from the current
Christian Heimes added the comment:
Python's extension modules aren't consistent. Some places deallocate the object
with PyObject_Del(), other places are using PyObject_GC_Del() or simple
Py_DECREF().
--
nosy: +christian.heimes
priority: normal - low
stage: - needs patch
type: -
Mark Lawrence breamore...@yahoo.co.uk added the comment:
Can someone in the know provide a doc patch for this?
--
assignee: georg.brandl - d...@python
nosy: +BreamoreBoy, d...@python
___
Python tracker rep...@bugs.python.org
New submission from Jean-Paul Calderone exar...@divmod.com:
Creation of GC'd types is explained at
http://docs.python.org/c-api/gcsupport.html.
The docs claim that PyObject_GC_Track must be called once an object
created with PyObject_GC_New is initialized. The docs fail to explain
what should
