-
Notifications
You must be signed in to change notification settings - Fork 532
Use reference to err to avoid deletion in Py3.4 #1551
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
Conversation
@oesteban how does this relate to your py3 efforts? |
In Circle we were not testing python 3.4. In travis it didn't complain. I guess there is no test to exercise that exception catching. |
Here is an MWE to demonstrate my issue.
Th important part of the log being:
This patch (replicating the PR) fixes it:
|
I realised I was using 12.0 in that last example, but the same error holds for 12.1
Similarly for Py3.3
|
Could you try current master? A lot of py3 improvements have been fixed On Thu, Sep 8, 2016 at 4:31 PM, Ashley Gillman [email protected]
|
On master (0f9a620)
I hadn't realised it was all the Py3 versions. It seems strange no one else has noticed this, can any one else replicate? |
Yes, the same happens to me. I didn't see it, since there is not test for this. Could you make a test from your MWE and push it along your fix? |
Test added, fails w/o change, passes with new change. |
Update on #1446, I was still getting an error on Python 3.4.4
See also PR #1447