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 eric.araujo
Recipients alexis, eric.araujo, tarek, vinay.sajip
Date 2011-10-19.20:05:36
SpamBayes Score 8.200918e-11
Marked as misclassified No
Message-id <1319054737.41.0.295237299107.issue13225@psf.upfronthosting.co.za>
In-reply-to
Content
As discussed in #11637, failing hooks should not stop operation.  I see different issues:

a) a hook is not found
b) a hook is not callable
c) a hook raises an exception

Current code will raise a Packaging exception for a) and b), and let the exception propagate in case of c).  I have a patch that makes Packaging ignore all three kinds and issue warning or error logging messages.

An option (--strict) would be needed to switch from logging messages to exceptions; I wonder if an elegant way to do that would be a custom logging handler.
History
Date User Action Args
2011-10-19 20:05:37eric.araujosetrecipients: + eric.araujo, vinay.sajip, tarek, alexis
2011-10-19 20:05:37eric.araujosetmessageid: <1319054737.41.0.295237299107.issue13225@psf.upfronthosting.co.za>
2011-10-19 20:05:36eric.araujolinkissue13225 messages
2011-10-19 20:05:36eric.araujocreate