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 Giovanni.Bajo, avian, bobbyi, gregory.p.smith, neologix, nirai, pitrou, sdaoden, vstinner
Date 2011-07-18.00:27:22
SpamBayes Score 8.698531e-07
Marked as misclassified No
Message-id <>
No Python thread is ever fork safe because the Python interpreter itself can never be made fork safe. Nor should anyone try to make the interpreter itself safe. It is too complex and effectively impossible to guarantee.

There is no general solution to this, fork and threading is simply broken in POSIX and no amount of duct tape outside of the OS kernel can fix it. My only desire is that we attempt to do the right thing when possible with the locks we know about within the standard library.
Date User Action Args
2011-07-18 00:27:23gregory.p.smithsetrecipients: + gregory.p.smith, pitrou, vstinner, nirai, bobbyi, neologix, Giovanni.Bajo, sdaoden, avian
2011-07-18 00:27:23gregory.p.smithsetmessageid: <>
2011-07-18 00:27:23gregory.p.smithlinkissue6721 messages
2011-07-18 00:27:22gregory.p.smithcreate