Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix exception causes in handlers.py #5530

Merged
merged 1 commit into from Jun 24, 2020
Merged

Conversation

cool-RR
Copy link
Contributor

@cool-RR cool-RR commented Jun 12, 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!

@kevin-bates
Copy link
Member

Hi @cool-RR - this seems like a useful set of changes that might better assist in troubleshooting efforts - thank you.

Would you also be interested in contributing this exercise to jupyter_server as well? The reason I bring that up is because if you were to make these changes in one of notebook or jupyter_server repos, it would probably be of higher value applied only to the latter (jupyter_server) - since that's more in the long-range plans of the ecosystem. However, if you'd like to apply to both repositories, these changes are more than welcome!

@cool-RR
Copy link
Contributor Author

cool-RR commented Jun 16, 2020

I put jupyter/jupyter_server on my list of repos to look at.

@cool-RR
Copy link
Contributor Author

cool-RR commented Jun 21, 2020

@Zsailer Would you like this change?

@kevin-bates
Copy link
Member

@cool-RR - this seems like a worthwhile endeavor for this repo. Would you mind cranking out the rest of the changes?

@cool-RR
Copy link
Contributor Author

cool-RR commented Jun 24, 2020

I prefer to do it after the initial PR is accepted, so if there are unexpected difficulties, they come up before I've done that work.

Copy link
Member

@kevin-bates kevin-bates left a comment

Choose a reason for hiding this comment

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

LGTM.

@kevin-bates kevin-bates merged commit db46c59 into jupyter:master Jun 24, 2020
@cool-RR
Copy link
Contributor Author

cool-RR commented Jun 24, 2020 via email

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 23, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants