Remove outdated ImportError check for warnings#279
Merged
Conversation
Contributor
Author
|
The change in 8c6015c is unrelated but seems to be necessary to satisfy the |
abravalheri
changed the title
ImportError check for warningsImportError check for warnings
Contributor
Author
|
The |
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
2 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.
If I am not mistaken
warningsis a valid import in any supported version of Python, so there is no need for handling anImportError.This seems to have been introduced in c3c5a89, 31th Oct 2002 (so the commit might have been accounting for versions of Python prior to 2.1, which was released on 17th Apr 2001).