➜

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 Birne94
Recipients Birne94, Connor.Wolf, Giovanni.Bajo, Winterflower, bobbyi, dan.oreilly, davin, emptysquare, forest_atq, gregory.p.smith, ionelmc, jcea, lesha, neologix, nirai, nirs, pitrou, sbt, sdaoden, tshepang, vinay.sajip, vstinner
Date 2017-05-31.11:40:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1496230853.19.0.358451789815.issue6721@psf.upfronthosting.co.za>
In-reply-to
Content 
While having to deal with this bug for a while I have written a small library using `pthread_atfork`: https://github.com/Birne94/python-atfork-lock-release

It allows registering atfork-hooks (similar to the ones available by now) and frees the stdout/stderr as well as manually provided io locks. I guess it uses some hacky ways to get the job done, but resolved the issue for me and has been working without problems for some weeks now.
History
Date User Action Args
2017-05-31 11:40:53Birne94setrecipients: + Birne94, gregory.p.smith, vinay.sajip, jcea, nirs, pitrou, vstinner, nirai, forest_atq, ionelmc, bobbyi, neologix, Giovanni.Bajo, sdaoden, tshepang, sbt, lesha, emptysquare, dan.oreilly, davin, Connor.Wolf, Winterflower
2017-05-31 11:40:53Birne94setmessageid: <1496230853.19.0.358451789815.issue6721@psf.upfronthosting.co.za>
2017-05-31 11:40:53Birne94linkissue6721 messages
2017-05-31 11:40:52Birne94create