Fix Python 3 TypeError when comparing string to None #4
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
|
|
carlio
added a commit
that referenced
this pull request
Mar 23, 2015
Fix Python 3 TypeError when comparing string to None
|
Thanks! This also fixes landscapeio/prospector#59 👍 |
carlio
added a commit
that referenced
this pull request
Mar 23, 2015
…vely: self.name or ("" > other.name)
carlio
added a commit
that referenced
this pull request
Mar 23, 2015
…vely: self.name or ("" > other.name)
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.
Python 3 produces "TypeError: unorderable types" when an attempt is made to compare a string with None, and that can happen in this bit of code, since the "name" attribute can be either a string or None. This fix ensures the comparison is always between strings.