Message 300723 - 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-08-22.22:05:09
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1503439509.06.0.137120149897.issue14976@psf.upfronthosting.co.za>
In-reply-to

Content
After experimenting a bit more with this approach, I now realize that the case where a get() is waiting and gets interrupted by a put() call is not handled properly: there is no obvious way for the get() call to realize (when the interruption finishes) that the queue is now non-empty and can be popped from. So perhaps we need C code after all.

After experimenting a bit more with this approach, I now realize that the case where a get() is waiting and gets interrupted by a put() call is not handled properly: there is no obvious way for the get() call to realize (when the interruption finishes) that the queue is now non-empty and can be popped from.

So perhaps we need C code after all.

History
Date	User	Action	Args
2017-08-22 22:05:09	pitrou	set	recipients: + pitrou, gvanrossum, tim.peters, rhettinger, ncoghlan, zzzeek, python-dev, sbt, serhiy.storchaka, JohanAR, yselivanov, itamarst, davin
2017-08-22 22:05:09	pitrou	set	messageid: <1503439509.06.0.137120149897.issue14976@psf.upfronthosting.co.za>
2017-08-22 22:05:09	pitrou	link	issue14976 messages
2017-08-22 22:05:09	pitrou	create