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 asksol, brandon-rhodes, catalin.iacob, cool-RR, dholth, jnoller, mrmekon, ned.deily, neologix, numbernine, pitrou, rcoyner, sbt, vsekhar
Date 2012-10-23.23:39:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
A use case for not using fork() is when your parent process opens some system resources of some sort (for example a listening TCP socket). The child will then inherit those resources, which can have all kinds of unforeseen and troublesome consequences (for example that listening TCP socket will be left open in the child when it is closed in the parent, and so trying to bind() to the same port again will fail).

Generally, I think having an option for zero-sharing spawning of processes would help code quality.
Date User Action Args
2012-10-23 23:39:13pitrousetrecipients: + pitrou, ned.deily, jnoller, rcoyner, asksol, cool-RR, dholth, brandon-rhodes, neologix, catalin.iacob, sbt, numbernine, vsekhar, mrmekon
2012-10-23 23:39:13pitrousetmessageid: <>
2012-10-23 23:39:13pitroulinkissue8713 messages
2012-10-23 23:39:13pitroucreate