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 exarkun
Recipients exarkun, georg.brandl
Date 2009-05-27.20:48:53
SpamBayes Score 9.3732175e-05
Marked as misclassified No
Message-id <1243457336.14.0.579311647458.issue6128@psf.upfronthosting.co.za>
In-reply-to
Content
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 be done if there is an error during initialization of an
object created with PyObject_GC_New.  Should PyObject_GC_Track still be
called?  Should some other API be called to free the object?

Overall, the docs are missing an explanation of the overall working of
the GC and GC APIs, so it is hard to build an understanding of the
system.  Without an understand, it's difficult to read between the lines
of the API docs, meaning they need to cover every possible case, which
they don't currently.
History
Date User Action Args
2009-05-27 20:48:56exarkunsetrecipients: + exarkun, georg.brandl
2009-05-27 20:48:56exarkunsetmessageid: <1243457336.14.0.579311647458.issue6128@psf.upfronthosting.co.za>
2009-05-27 20:48:54exarkunlinkissue6128 messages
2009-05-27 20:48:53exarkuncreate