➜

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 DLitz
Recipients Arfrever, DLitz, aliles, amaury.forgeotdarc, asvetlov, christian.heimes, georg.brandl, grahamd, gregory.p.smith, jcea, lemburg, neologix, pitrou, sbt, twouters, vstinner
Date 2013-10-21.13:42:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1382362966.58.0.793968466399.issue16500@psf.upfronthosting.co.za>
In-reply-to
Content 
> The main question is whether a failed prepare callback should prevent the fork from happenning

Yes, I think an exception should prevent the fork from happening.

It's fail-safe for the PRNG case (you can guarantee that a fork won't occur without properly re-seeding a PRNG), and it makes bugs easier to catch in unit testing.
History
Date User Action Args
2013-10-21 13:42:46DLitzsetrecipients: + DLitz, lemburg, twouters, georg.brandl, gregory.p.smith, jcea, amaury.forgeotdarc, pitrou, vstinner, christian.heimes, grahamd, Arfrever, asvetlov, neologix, sbt, aliles
2013-10-21 13:42:46DLitzsetmessageid: <1382362966.58.0.793968466399.issue16500@psf.upfronthosting.co.za>
2013-10-21 13:42:46DLitzlinkissue16500 messages
2013-10-21 13:42:46DLitzcreate