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 barry, benjamin.peterson, christian.heimes, georg.brandl, neologix, pitrou, python-dev, sbt, vajrasky, vstinner
Date 2013-08-22.15:20:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
> IMO this patch has been rushed in and should be reverted for now.
> It's still not async-signal safe, had typos, plus this problem noted
> by Victor.

That's not really a problem. You merely have to *perturb* the random
state in the parent, so that the next child gets a different initial
state. As pointed out in a mailing-list message, mixing in a constant
could be enough to perturb the state.

As for not being async-signal safe, it's only in the double fork()
case, which is much less of an issue IMO.
Date User Action Args
2013-08-22 15:20:15pitrousetrecipients: + pitrou, barry, georg.brandl, vstinner, christian.heimes, benjamin.peterson, neologix, python-dev, sbt, vajrasky
2013-08-22 15:20:15pitroulinkissue18747 messages
2013-08-22 15:20:14pitroucreate