Author gregory.p.smith
Recipients cagney, gregory.p.smith, ned.deily, vstinner
Date 2019-04-05.09:02:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
A stdlib alternative to this whole mess would be to avoid acquiring the logging locks before fork() as we currently do and just blindly re-initialize all of them afterwards under the assumption that they "can't" be protecting anything in a newly forked child process.  Handlers that need specific resource synchronization around fork would then be required to deal with their own os.register_at_fork() calls.  (ex: to avoid multiple processes writing to the same file or fd at once)
Date User Action Args
2019-04-05 09:02:41gregory.p.smithsetrecipients: + gregory.p.smith, vstinner, ned.deily, cagney
2019-04-05 09:02:41gregory.p.smithsetmessageid: <>
2019-04-05 09:02:41gregory.p.smithlinkissue36533 messages
2019-04-05 09:02:41gregory.p.smithcreate