Author christian.heimes
Recipients amaury.forgeotdarc, asvetlov, christian.heimes, gregory.p.smith, sbt, twouters
Date 2012-11-20.16:20:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1353428442.63.0.881675690516.issue16500@psf.upfronthosting.co.za>
In-reply-to
Content
Amaury:
PyPy doesn't handle exceptions in hooks. Is there a reason why PyPy goes for the simplistic approach?

Richard:
An error callback has the benefit that the API can notice the hooks that some error has occurred. We may not need it, though.

I can think of six exception scenarios that must be handled:

(1) exception in a prepare hook -> don't call the remaining prepare hooks, run all related parent hooks in FILO order, prevent fork() call
(2) exception in parent hook during the handling of (1) -> print exception, continue with next parent hook
(3) exception in fork() call -> run parent hooks in FILO order
(4) exception in parent hook during the handling of (3) -> print exception, continue with next parent hook
(5) exception in parent hook when fork() has succeeded -> print exception, continue with next parent hook
(6) exception in child hook when fork() has succeeded  -> print exception, continue with next child hook

Do you agree?
History
Date User Action Args
2012-11-20 16:20:42christian.heimessetrecipients: + christian.heimes, twouters, gregory.p.smith, amaury.forgeotdarc, asvetlov, sbt
2012-11-20 16:20:42christian.heimessetmessageid: <1353428442.63.0.881675690516.issue16500@psf.upfronthosting.co.za>
2012-11-20 16:20:42christian.heimeslinkissue16500 messages
2012-11-20 16:20:42christian.heimescreate