bpo-39164: Fix compiler warning in PyErr_GetExcInfo()#18010
Merged
Conversation
The function has no return value.
ammaraskar
approved these changes
Jan 15, 2020
jd
approved these changes
Jan 15, 2020
Member
Author
|
Documenation job of Travis CI failed with a network issue on NNTP('news.gmane.io'): https://bugs.python.org/issue39343 It's an unrelated issue. |
Member
Author
|
@ammaraskar: Thanks for the warning report! |
sthagen
added a commit
to sthagen/python-cpython
that referenced
this pull request
Jan 15, 2020
bpo-39164: Fix compiler warning in PyErr_GetExcInfo() (pythonGH-18010)
shihai1991
pushed a commit
to shihai1991/cpython
that referenced
this pull request
Jan 31, 2020
The function has no return value.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The function has no return value.
https://bugs.python.org/issue39164