Message 301321 - 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	pitrou
Recipients	JohanAR, davin, gvanrossum, itamarst, ncoghlan, pitrou, python-dev, rhettinger, sbt, serhiy.storchaka, tim.peters, yselivanov, zzzeek
Date	2017-09-05.15:50:58
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<[email protected]>
In-reply-to

Content
> Would it make sense get() and put() to add gc.disable() and gc.enable() whenever GC is already enabled? That doesn't sound very nice if some thread is waiting on a get() for a very long time (which is reasonable if you have a thread pool that's only used sporadically, for example). Also, using gc.disable() and gc.enable() in multi-threaded programs is a bit delicate.

> Would it make sense get() and put() to add gc.disable() and gc.enable() whenever GC is already enabled?

That doesn't sound very nice if some thread is waiting on a get() for a very long time (which is reasonable if you have a thread pool that's only used sporadically, for example).  Also, using gc.disable() and gc.enable() in multi-threaded programs is a bit delicate.

History
Date	User	Action	Args
2017-09-05 15:50:58	pitrou	set	recipients: + pitrou, gvanrossum, tim.peters, rhettinger, ncoghlan, zzzeek, python-dev, sbt, serhiy.storchaka, JohanAR, yselivanov, itamarst, davin
2017-09-05 15:50:58	pitrou	set	messageid: <[email protected]>
2017-09-05 15:50:58	pitrou	link	issue14976 messages
2017-09-05 15:50:58	pitrou	create