Skip to content

Fix exception causes in lexer.py#1478

Merged
birkenfeld merged 1 commit into
pygments:masterfrom
cool-RR:2020-06-11-raise-from
Jun 20, 2020
Merged

Fix exception causes in lexer.py#1478
birkenfeld merged 1 commit into
pygments:masterfrom
cool-RR:2020-06-11-raise-from

Conversation

@cool-RR
Copy link
Copy Markdown
Contributor

@cool-RR cool-RR commented Jun 11, 2020

I recently went over Matplotlib, Pandas and NumPy, fixing a small mistake in the way that Python 3's exception chaining is used. If you're interested, I can do it here too. I've done it on just one file right now.

The mistake is this: In some parts of the code, an exception is being caught and replaced with a more user-friendly error. In these cases the syntax raise new_error from old_error needs to be used.

Python 3's exception chaining means it shows not only the traceback of the current exception, but that of the original exception (and possibly more.) This is regardless of raise from. The usage of raise from tells Python to put a more accurate message between the tracebacks. Instead of this:

During handling of the above exception, another exception occurred:

You'll get this:

The above exception was the direct cause of the following exception:

The first is inaccurate, because it signifies a bug in the exception-handling code itself, which is a separate situation than wrapping an exception.

Let me know what you think!

Copy link
Copy Markdown
Member

@birkenfeld birkenfeld left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks.

@cool-RR
Copy link
Copy Markdown
Contributor Author

cool-RR commented Jun 19, 2020

Nudge.

@birkenfeld birkenfeld merged commit f751358 into pygments:master Jun 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants