bpo-35476: clear error in _imp_create_dynamic_impl#14738
Conversation
brettcannon
left a comment
There was a problem hiding this comment.
I don't think this is quite doing what @ericsnowcurrently meant when he said "the error should be cleared" as an option in the issue. Instead, I believe what he was thinking was that there be an elif (PyErr_Occurred()) clause to go after the if (mod != NULL) which then clears the exception.
Sorry, something went wrong.
|
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase |
Sorry, something went wrong.
|
I'm going to kick off a discussion over on the issue which I think may change the approach this PR takes. |
Sorry, something went wrong.
|
@isidentical please note the conversation on the issue is advocating for explicit exception raising, so that changes the approach you've taken here. |
Sorry, something went wrong.
|
CLosing as @ericsnowcurrently pointed out the current semantics cover the bug. |
Sorry, something went wrong.
clear error in _imp_create_dynamic_impl
https://bugs.python.org/issue35476