➜

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 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:02:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1382360532.86.0.601550711219.issue16500@psf.upfronthosting.co.za>
In-reply-to
Content 
> Richard, do you have time to get your patch ready for 3.4? Yes. But we don't seem to have concensus on how to handle exceptions. The main question is whether a failed prepare callback should prevent the fork from happenning, or just be printed.
History
Date User Action Args
2013-10-21 13:02:12sbtsetrecipients: + sbt, lemburg, twouters, georg.brandl, gregory.p.smith, jcea, amaury.forgeotdarc, pitrou, vstinner, christian.heimes, grahamd, Arfrever, asvetlov, neologix, aliles, DLitz
2013-10-21 13:02:12sbtsetmessageid: <1382360532.86.0.601550711219.issue16500@psf.upfronthosting.co.za>
2013-10-21 13:02:12sbtlinkissue16500 messages
2013-10-21 13:02:12sbtcreate