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 serhiy.storchaka
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.14:08:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
PyOS_AfterFork() is used by one code, but the "before" and "parent" handlers are registered by the other code (likely the code of other library). The author of the program that uses both libraries (the one that uses PyOS_AfterFork() and the one that registers handlers) can notice the warning and report the bug in the first library. I think silently skipping registered handlers would be worse.

Let allow the user to control the behavior by setting the warnings filter. If the corresponding warnings are ignored, nothing happen, if they are errors, the child is exited, otherwise the warning message is output on stderr as for other warnings.
Date User Action Args
2017-05-22 14:08:16serhiy.storchakasetrecipients: + serhiy.storchaka, lemburg, twouters, georg.brandl, gregory.p.smith, jcea, amaury.forgeotdarc, pitrou, vstinner, christian.heimes, grahamd, Arfrever, ionelmc, asvetlov, neologix, socketpair, sbt, aliles, yselivanov, DLitz, emptysquare, xupeng, rpcope1
2017-05-22 14:08:16serhiy.storchakasetmessageid: <>
2017-05-22 14:08:16serhiy.storchakalinkissue16500 messages
2017-05-22 14:08:16serhiy.storchakacreate