A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2002-March/021535.html below:

[Python-Dev] Re: PEP 282 comments

[Python-Dev] Re: PEP 282 commentsVinay Sajip vinay_sajip@red-dove.com
Thu, 21 Mar 2002 02:48:22 -0000
[Trent]
>     try:
>         ...
>     except:
>         log.exception("My britches are burning!")
>
> sure is a log nicer than
>
>     try:
>         ...
>     except:
>         log.logException(sys.exc_info(), "My britches are burning!")
>
But you don't need to use the latter. For logging exceptions with a level of
ERROR, the former construction works. For the case where you want to log an
exception with (e.g.) a DEBUG level, then you would say

log.logException(DEBUG, sys.exc_info(), "My britches are burning!")

A little long-winded, perhaps, but not *that* bad. It has the benefit of
making it clear that even though it's a DEBUG level call, exception info is
to be sent to the log. Even in Jeremy's example of ZODB/ZEO, I would imagine
that the number of instances where you need to make the second kind of
logging call are relatively (i.e. proportionately) few - from his
explanation I infer that he was talking about "catch-all" exception handlers
which are usually at the higher levels of an application.

Anyway, to change the subject a bit, what are your thoughts on
configuration? As this is the area where the PEP and the present
implementation are both a little weak, I'd like to know more about your
ideas...

Regards

Vinay




RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4