Author vstinner
Recipients Dennis Sweeney, SD, eryksun, lunixbochs2, miss-islington, ned.deily, paul.moore, pitrou, steve.dower, tim.golden, vstinner, zach.ware
Date 2021-06-14.20:52:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1623703949.64.0.408900047802.issue41299@roundup.psfhosted.org>
In-reply-to
Content
> My read is that as long as we're not confident enough to remove those checks from pytime.c, a caller should assume they're reachable. If the pytime checks need to stay, adding a Windows only pytime init check to make sure that locks won't deadlock sounds fine to me.

If you consider that the risk is non-zero, you can add a check at startup.

Do you expect that a startup check is enough, or do you expect failures later?

I understood that if the first call succeed, later calls are very unlikely to fail. The first call should be enough to check for all possible errors.
History
Date User Action Args
2021-06-14 20:52:29vstinnersetrecipients: + vstinner, paul.moore, pitrou, tim.golden, ned.deily, zach.ware, eryksun, steve.dower, miss-islington, Dennis Sweeney, SD, lunixbochs2
2021-06-14 20:52:29vstinnersetmessageid: <1623703949.64.0.408900047802.issue41299@roundup.psfhosted.org>
2021-06-14 20:52:29vstinnerlinkissue41299 messages
2021-06-14 20:52:29vstinnercreate