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

Showing content from http://mail.python.org/pipermail/python-dev/2003-January/032494.html below:

[Python-Dev] Idea for avoiding exception masking

• Previous message: [Python-Dev] Idea for avoiding exception masking
• Next message: [Python-Dev] Idea for avoiding exception masking
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> On Tue, 28 Jan 2003, Raymond Hettinger wrote:
> > Python code has a number of cases where a higher
> > level routine traps an exception and reraises it with
> > new information and losing the lower level error
> > detail in the process.
> 
> How about just holding on to the original exception and
> storing it as an attribute (e.g. "cause") on the new exception?
> 
> 
> -- ?!ng

I was just thinking in terms of the error message,
but your way is cleaner and more comprehensive.


Raymond Hettinger

• Previous message: [Python-Dev] Idea for avoiding exception masking
• Next message: [Python-Dev] Idea for avoiding exception masking
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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