Message 306076 - Python tracker

➜

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	ncoghlan
Recipients	eric.snow, gregory.p.smith, josh.r, lisroach, ncoghlan, pablogsal, pitrou, rhettinger, serhiy.storchaka
Date	2017-11-11.06:04:54
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1510380295.13.0.213398074469.issue31356@psf.upfronthosting.co.za>
In-reply-to

Content
Given the existing "gc.enable", "gc.disable" and "gc.isenabled" APIs, I'd suggest calling this one "gc.ensure_disabled": it ensures the GC is disabled in the with statement body, but only turns it back on at the end if it was previously enabled. That same name would then be used all the way through the code and documentation.

Given the existing "gc.enable", "gc.disable" and "gc.isenabled" APIs, I'd suggest calling this one "gc.ensure_disabled": it ensures the GC is disabled in the with statement body, but only turns it back on at the end if it was previously enabled.

That same name would then be used all the way through the code and documentation.

History
Date	User	Action	Args
2017-11-11 06:04:55	ncoghlan	set	recipients: + ncoghlan, rhettinger, gregory.p.smith, pitrou, eric.snow, serhiy.storchaka, josh.r, lisroach, pablogsal
2017-11-11 06:04:55	ncoghlan	set	messageid: <1510380295.13.0.213398074469.issue31356@psf.upfronthosting.co.za>
2017-11-11 06:04:55	ncoghlan	link	issue31356 messages
2017-11-11 06:04:54	ncoghlan	create