➜

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 pitrou
Recipients Arfrever, DLitz, aliles, amaury.forgeotdarc, asvetlov, christian.heimes, emptysquare, georg.brandl, grahamd, gregory.p.smith, ionelmc, jcea, lemburg, neologix, pitrou, rpcope1, sbt, serhiy.storchaka, socketpair, twouters, vstinner, xupeng, yselivanov
Date 2017-05-22.15:36:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1495467382.56.0.170391686392.issue16500@psf.upfronthosting.co.za>
In-reply-to
Content 
> If the corresponding warnings are ignored, nothing happen, if they are errors, the child is exited,

Right now PyOS_AfterFork() doesn't return an error code.  It is not obvious how the caller would react: simply print the error? raise a fatal error? Something else?

The only third-party use of PyOS_AfterFork() I found is in uwsgi (and I'm not sure they're using it correctly, since I don't know if the parent process is using Python at all...).
History
Date User Action Args
2017-05-22 15:36:22pitrousetrecipients: + pitrou, lemburg, twouters, georg.brandl, gregory.p.smith, jcea, amaury.forgeotdarc, vstinner, christian.heimes, grahamd, Arfrever, ionelmc, asvetlov, neologix, socketpair, sbt, aliles, serhiy.storchaka, yselivanov, DLitz, emptysquare, xupeng, rpcope1
2017-05-22 15:36:22pitrousetmessageid: <1495467382.56.0.170391686392.issue16500@psf.upfronthosting.co.za>
2017-05-22 15:36:22pitroulinkissue16500 messages
2017-05-22 15:36:22pitroucreate