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/2013-May/126389.html below:

[Python-Dev] PEP 409 and the stdlib

[Python-Dev] PEP 409 and the stdlib [Python-Dev] PEP 409 and the stdlibEthan Furman ethan at stoneleaf.us
Mon May 20 15:12:41 CEST 2013
As a quick reminder, PEP 409 allows this:

     try:
         ...
     except AnError:
         raise SomeOtherError from None

so that if the exception is not caught, we get the traditional single exception traceback, instead of the new:

     During handling of the above exception, another exception occurred


My question:

How do we go about putting this in the stdlib?  Is this one of the occasions where we don't do it unless we're modifying 
a module already for some other reason?

For that matter, should we?

Pros:  Makes tracebacks much less confusing, especially coming from a library

Cons:  Could hide bugs unrelated to what is being caught and transformed

--
~Ethan~
More information about the Python-Dev mailing list

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