➜

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

Probably because nobody thought about it.
At the moment, there is only one 'before', one 'parent' hook (so the FILO order is simple), and three 'child' hooks.
And if the _PyImport_ReleaseLock call fails, you'd better not ignore the error...
History
Date User Action Args
2012-11-20 16:29:10amaury.forgeotdarcsetrecipients: + amaury.forgeotdarc, twouters, gregory.p.smith, christian.heimes, asvetlov, sbt
2012-11-20 16:29:10amaury.forgeotdarcsetmessageid: <1353428950.38.0.553053211459.issue16500@psf.upfronthosting.co.za>
2012-11-20 16:29:10amaury.forgeotdarclinkissue16500 messages
2012-11-20 16:29:10amaury.forgeotdarccreate