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.13:49:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1495460948.56.0.79248079683.issue16500@psf.upfronthosting.co.za>
In-reply-to
Content
I don't think exiting would be a good idea at all.  I'm not sure about emitting a warning: the problem is that the people seeing the warning (plain users) can't do anything about it; worse, they probably will not even understand what it is about, and will get confused.

The package maintainer should see a deprecation warning when compiling code using PyOS_AfterFork() (thanks to the Py_DEPRECATED attribute).

Of course, I'll also update the docs to add a deprecation once the design is settled.
History
Date User Action Args
2017-05-22 13:49:08pitrousetrecipients: + 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 13:49:08pitrousetmessageid: <1495460948.56.0.79248079683.issue16500@psf.upfronthosting.co.za>
2017-05-22 13:49:08pitroulinkissue16500 messages
2017-05-22 13:49:08pitroucreate