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 eryksun, neologix, paul.moore, pdgoins-work, pitrou, steve.dower, tim.golden, tim.peters, tupl, vstinner, zach.ware
Date 2018-04-30.21:39:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1525124354.84.0.682650639539.issue21822@psf.upfronthosting.co.za>
In-reply-to
Content
> I'm guessing this is because of the perceived performance impact?

The problem is polling is pretty detrimental to power saving on modern CPUs.  There might also be a performance impact that makes things worse :-)

More generally, we really would like locks to be interruptible under Windows, as it would be useful in many more situations than joining threads. Unfortunately, as you have discovered we have several lock implementations for Windows right now.  The SRWLock one is probably difficult to make interruptible, but it's never enabled by default.  The Semaphore one looks legacy, so could perhaps be removed.  Remains the condition variable-based implementation.
History
Date User Action Args
2018-04-30 21:39:14pitrousetrecipients: + pitrou, tim.peters, paul.moore, vstinner, tim.golden, neologix, zach.ware, eryksun, steve.dower, tupl, pdgoins-work
2018-04-30 21:39:14pitrousetmessageid: <1525124354.84.0.682650639539.issue21822@psf.upfronthosting.co.za>
2018-04-30 21:39:14pitroulinkissue21822 messages
2018-04-30 21:39:14pitroucreate