removed singleton comparison pitfall from the code#42
Open
NaelsonDouglas wants to merge 1 commit intoa1studmuffin:masterfrom
Open
removed singleton comparison pitfall from the code#42NaelsonDouglas wants to merge 1 commit intoa1studmuffin:masterfrom
NaelsonDouglas wants to merge 1 commit intoa1studmuffin:masterfrom
Conversation
|
Why? |
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.
The problem
In Python when comparing a variable to a singleton value like True, False and None it is advised to use the operator 'is' instead of '=='. This pitfall was detected using Pylint, which indicated it under the code C0121, as seen on the link below
https://vald-phoenix.github.io/pylint-errors/plerr/errors/basic/C0121.html
The solution
Just changed the operator