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 gregory.p.smith
Recipients Connor.Wolf, Giovanni.Bajo, bobbyi, dan.oreilly, emptysquare, forest_atq, gregory.p.smith, ionelmc, jcea, lesha, neologix, nirai, nirs, pitrou, sbt, sdaoden, tshepang, vinay.sajip, vstinner
Date 2016-07-09.03:19:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
For me the momentum on fixing these things has stalled because I no longer work on any code that runs into this.  There is a fundamental problem: You cannot safely use threading and os.fork() in the same application per POSIX rules.  So even if the standard library and interpreter to tried to force its locks into some sort of consistent state post os.fork(), the much more fundamental POSIX problem remains.

IMNSHO, working on "fixes" for this issue while ignoring the larger application design flaw elephant in the room doesn't make a lot of sense.
Date User Action Args
2016-07-09 03:19:21gregory.p.smithsetrecipients: + gregory.p.smith, vinay.sajip, jcea, nirs, pitrou, vstinner, nirai, forest_atq, ionelmc, bobbyi, neologix, Giovanni.Bajo, sdaoden, tshepang, sbt, lesha, emptysquare, dan.oreilly, Connor.Wolf
2016-07-09 03:19:21gregory.p.smithsetmessageid: <>
2016-07-09 03:19:21gregory.p.smithlinkissue6721 messages
2016-07-09 03:19:20gregory.p.smithcreate