[issue13225] Failing packaging hooks should not stop operation

2014-03-12 Thread Éric Araujo

Éric Araujo added the comment:

Out of date for distutils2, may be considered for metadata 2.0 hooks.

--
nosy: +ncoghlan
resolution:  - out of date
stage:  - committed/rejected
status: open - closed

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13225
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue13225] Failing packaging hooks should not stop operation

2011-10-19 Thread Éric Araujo

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



[issue13225] Failing packaging hooks should not stop operation

2011-10-19 Thread Vinay Sajip

Vinay Sajip vinay_sa...@yahoo.co.uk added the comment:

 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.

I'm not sure a custom logging handler is the way to go. I think it would be 
better to log the exception condition in all cases, raising it if --strict is 
specified, and swallowing it otherwise. An application developer can configure 
loggers/handlers appropriately if they want.

--

___
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