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 llllllllll
Recipients llllllllll
Date 2016-09-23.06:21:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1474611707.66.0.467568151114.issue28254@psf.upfronthosting.co.za>
In-reply-to
Content
I was writing an extension module that was working with weakrefs and wanted to ensure that the GC would not run for a block of code. I noticed that gc.enable/gc.disable are not exposed to C and the state of the gc is in a static variable so it cannot be mutated from an extension.

This change adds an easier way to access this functionality in the C api without going through an import or PyObject_Call.

I am wondering where to document these functions as well as PyGC_Collect. I didn't see that function anywhere in the docs (and didn't know about it) so I would like to make them more visible. My first thought was Doc/c-api/gcsupport.rst but this is not in service of supporting the GC, it is about the state of the GC itself. If that seems like a decent place I could add a small section at the bottom about interacting with the GC and document these new functions and PyGC_Collect.

I'm sorry if this is exposed elsewhere. If it is I can try to add some links to i
History
Date User Action Args
2016-09-23 06:21:47llllllllllsetrecipients: + llllllllll
2016-09-23 06:21:47llllllllllsetmessageid: <1474611707.66.0.467568151114.issue28254@psf.upfronthosting.co.za>
2016-09-23 06:21:47lllllllllllinkissue28254 messages
2016-09-23 06:21:46llllllllllcreate