Message301321
| 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 |
<1504626658.51.0.126899430359.issue14976@psf.upfronthosting.co.za> |
| 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. |
|
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: <1504626658.51.0.126899430359.issue14976@psf.upfronthosting.co.za> |
| 2017年09月05日 15:50:58 | pitrou | link | issue14976 messages |
| 2017年09月05日 15:50:58 | pitrou | create |
|