➜

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.13:41:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1495460482.41.0.288785422397.issue16500@psf.upfronthosting.co.za>
In-reply-to
Content 
I agree that with lambdas and functools.partial the support of arguments is not needed. Unless someone has good reasons for supporting explicit passing of arguments I'm fine with your design.

If the user code manually calls the fork() and (now deprecated) PyOS_AfterFork(), it runs "child" functions, but not "before" and "parent" functions. Is it worth to emit a runtime warning if the "before" or "parent" lists are not empty? Or even immediately exit a child with error?
History
Date User Action Args
2017-05-22 13:41:22serhiy.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 13:41:22serhiy.storchakasetmessageid: <1495460482.41.0.288785422397.issue16500@psf.upfronthosting.co.za>
2017-05-22 13:41:22serhiy.storchakalinkissue16500 messages
2017-05-22 13:41:22serhiy.storchakacreate