➜

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 christian.heimes
Recipients benjamin.peterson, christian.heimes, georg.brandl, larry, neologix, pitrou, python-dev, r.david.murray, sbt, vstinner
Date 2013-10-26.15:42:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1382802137.56.0.820061843946.issue19227@psf.upfronthosting.co.za>
In-reply-to
Content 
I still don't get it. All arguments are about "don't execute async unsafe code after fork()". But the child process does *not* execute *any* code after fork. It's just the parent process that executes its handler.
History
Date User Action Args
2013-10-26 15:42:17christian.heimessetrecipients: + christian.heimes, georg.brandl, pitrou, vstinner, larry, benjamin.peterson, r.david.murray, neologix, python-dev, sbt
2013-10-26 15:42:17christian.heimessetmessageid: <1382802137.56.0.820061843946.issue19227@psf.upfronthosting.co.za>
2013-10-26 15:42:17christian.heimeslinkissue19227 messages
2013-10-26 15:42:17christian.heimescreate