Changed all "== None" and "!= None" #89
Merged
Conversation
This file contains 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
… stop python 2.7 from giving FutureWarning: comparison to `None` will result in an elementwise object comparison in the future.
|
Thanks very much, I usually don't do this mistake, these lines are either not my code or have been written very late in the night ;) |
Zulko
added a commit
that referenced
this pull request
Nov 21, 2014
Changed all "== None" and "!= None" to resp. "is None" and "is not None"
|
Thank YOU for moviepy and accepting my pull request! On 21/11/2014 16:47, Zulko wrote:
Il messaggio e' stato analizzato alla ricerca di virus o |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Changed all "== None" and "!= None" occurrences to comply to PEP8 and stop python 2.7 from giving FutureWarning: comparison to
Nonewill result in an elementwise object comparison in the future.Hi Zulko, just a small "style" change, if you find it useful...