Message 145950 - Python tracker

➜

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.

In-reply-to
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>

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.

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:37	eric.araujo	set	recipients: + eric.araujo, vinay.sajip, tarek, alexis
2011年10月19日 20:05:37	eric.araujo	set	messageid: <1319054737.41.0.295237299107.issue13225@psf.upfronthosting.co.za>
2011年10月19日 20:05:36	eric.araujo	link	issue13225 messages
2011年10月19日 20:05:36	eric.araujo	create

homepage