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 zmqshell.py #516

Merged
merged 1 commit into from
Jun 12, 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!

@blink1073
Copy link
Contributor

Hi @cool-RR, thanks for bringing this up. Yes, this change would be most welcome!

@blink1073 blink1073 added this to the 5.4 milestone Jun 12, 2020
@cool-RR
Copy link
Contributor Author

cool-RR commented Jun 12, 2020

Awesome! After this PR is merged, I'll do the rest.

@blink1073
Copy link
Contributor

We can do them in one PR, it will be easier to track in the changelog.

@cool-RR
Copy link
Contributor Author

cool-RR commented Jun 12, 2020

I looked at the other places now, which is actually just one file backend_inline.py, and found that the matches there were false positives. So it looks like this project has only the two instances that I fixed in this PR.

@blink1073
Copy link
Contributor

Cool, thanks!

@blink1073 blink1073 merged commit 8ec2c46 into ipython:master Jun 12, 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