New submission from Éric Araujo <mer...@netwok.org>: 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. ---------- assignee: eric.araujo components: Distutils2 messages: 145950 nosy: alexis, eric.araujo, tarek, vinay.sajip priority: normal severity: normal status: open title: Failing packaging hooks should not stop operation versions: 3rd party, Python 3.3 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue13225> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
