➜

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 sbt
Recipients barry, benjamin.peterson, christian.heimes, georg.brandl, neologix, pitrou, python-dev, sbt, vstinner
Date 2013-08-21.15:27:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <5214DC5D.6020002@gmail.com>
In-reply-to <CAH_1eM1bmgDkyXVLgd7-Q+F57JCMVMj=LVHdeJO9AWHuXkWJSQ@mail.gmail.com>
Content 
On 21/08/2013 3:46pm, Charles-François Natali wrote:
> Another, probably cleaner way would be to finally add the atfork()
> module (issue #16500), and register this reseed hook (which could then
> be implemented in ssl.py).

Wouldn't that still suffer from the double-fork() issue?
History
Date User Action Args
2013-08-21 15:27:33sbtsetrecipients: + sbt, barry, georg.brandl, pitrou, vstinner, christian.heimes, benjamin.peterson, neologix, python-dev
2013-08-21 15:27:33sbtlinkissue18747 messages
2013-08-21 15:27:33sbtcreate