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 josh.r
Recipients josh.r, miles, milesli
Date 2019-04-17.19:03:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1555527822.13.0.166565254554.issue23382@roundup.psfhosted.org>
In-reply-to
Content
Correct me if I'm wrong, but this isn't actually an issue for CPython, right? The GIL ensures that when a thread writes to _shutdown, nothing else is reading it until the GIL is released and acquired by a new thread (which synchronizes _shutdown).

It might conceivably be a problem on non-CPython interpreters if they have no other form of inter-thread synchronization involved; that said, the locking involved in the self.work_queue.get(block=True) call likely synchronizes by side-effect even there.
History
Date User Action Args
2019-04-17 19:03:42josh.rsetrecipients: + josh.r, miles, milesli
2019-04-17 19:03:42josh.rsetmessageid: <1555527822.13.0.166565254554.issue23382@roundup.psfhosted.org>
2019-04-17 19:03:42josh.rlinkissue23382 messages
2019-04-17 19:03:42josh.rcreate