Change tests assertIs(..., True) for assertTrue(...)
Predicate functions shouldn't convert its implementation based on
logic expressions (combinations of `not`, `and` and `or`).
I.e. The following should be correct:
def is_NOT_divisible_by_4(n):
return n % 4
assert is_NOT_divisible_by_4(10)
But as the TestCases for this exercise are using `assertIs(..., True)
instead of `assertTrue(...)`, implementations cointing on the numbers
behaviour on boolean contexts will Fail.
What this mean, is that for the given definition of
`is_NOT_divisible_by_4`, the folloging assertion will Fail:
assert is_NOT_divisible_by_4(10) == True
I think it is meaningless to check for `True` as it is naive to write:
if predicate(x) == True:
do_something(x)
Instead of:
if predicate(x):
do_something(x)
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
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.
leap: Change tests assertIs(..., True) for assertTrue(...) #419
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uh oh!
There was an error while loading. Please reload this page.
leap: Change tests assertIs(..., True) for assertTrue(...) #419
Filter by extension
Viewed files
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Predicate functions shouldn't convert its implementation based on logic expressions (combinations of `not`, `and` and `or`). I.e. The following should be correct: def is_NOT_divisible_by_4(n): return n % 4 assert is_NOT_divisible_by_4(10) But as the TestCases for this exercise are using `assertIs(..., True) instead of `assertTrue(...)`, implementations cointing on the numbers behaviour on boolean contexts will Fail. What this mean, is that for the given definition of `is_NOT_divisible_by_4`, the folloging assertion will Fail: assert is_NOT_divisible_by_4(10) == True I think it is meaningless to check for `True` as it is naive to write: if predicate(x) == True: do_something(x) Instead of: if predicate(x): do_something(x)Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing