Repository navigation
Ignore PendingDeprecationWarning from Coverage - #650
Merged
Merged
Conversation
…g the imp module. This warning causes 3.4 builds to fail so ignore the warning from importing coverage.
wiredfool
added a commit
that referenced
this pull request
May 9, 2014
Ignore PendingDeprecationWarning from Coverage for Py 3.4
Member
|
Thanks Hugo. |
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.
PendingDeprecationWarnings are coming from Coverage.py, specificallyimport coverageon line 348 of tester.py:https://github.com/python-imaging/Pillow/blob/master/Tests/tester.py#L348
Coverage.py, execfile.py, line 3,
import imp:https://github.com/nedbat/coveragepy/blob/master/coverage/execfile.py#L3
Let's ignore the warning from Coveralls for now so we can have Python 3.4 as a must-pass.
This resolves #592.
I've reported the warning to Coverage.py.