-
Notifications
You must be signed in to change notification settings - Fork 42
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
Handling NameError is not working #129
Comments
@shazarivf Thasnks - I agree that this looks wrong. I'll need to investigate, and I can't look at this in depth this week and can't promise this will be fixed quickly. Does undoing that check of |
@newville yes, removing the check fixes it. I can raise a PR if you think the check is safe to remove |
@shazarivf Yes please -- I'd be interested to see what tests fail! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We recently upgraded to a new version and we have a several scripts that relied on handling NameError as we couldn't ensure all user_symbols to be present always.
The following is a small example snippet doesn't work as expected anymore.
This results in:
NameError doesn't get handled and the code just breaks and returns None
It looks like this behavior changed with version 0.9.17 and this commit.
The text was updated successfully, but these errors were encountered: