-
Notifications
You must be signed in to change notification settings - Fork 409
New issue
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
[MRG] Remove pytest warnings due to yield based tests. #461
Conversation
Oops, github assumed the commit message as PR title already ! |
Before I forget it would be good to remove |
e381ce0
to
8bc8899
Compare
8bc8899
to
33275b1
Compare
With test_memory.py and test_parallel.py done, we are already at 36 warnings already! |
@lesteve ZERO WARNINGS ! 🏁 💚 |
yield check_same_results, dict(n_tasks=25, n_jobs=4, batch_size=7) | ||
yield check_same_results, dict(n_tasks=10, n_jobs=4, | ||
pre_dispatch="2*n_jobs") | ||
check_same_results({'n_tasks': 2, 'n_jobs': 2, 'pre_dispatch': "all"}) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nitpick: typically you could have left the dict
here. My personal preference is for the dict literal i.e. {'a': 1, 'b': 2}
. Some people like dict
apparently because it is more obvious to spot than {}
and you don't have to type quotes around the keys. Basically: no strong motivation or no strong consensus -> leave it as it is.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My motivation is to keep things as uniform as possible, throughout the codebase. Maybe I will tune down its "intensity" 😁
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah it's a very fine equilibrium to find sometimes.
NIce very tidy ouput, I like this, great stuff, merging! |
Fourth Phase PR on #411
This PR targets on completely removing all the pytest warnings existing in all the tests at this stage. On
master
, at the base of this PR, there are 189 pytest warnings - mostly because pytest >= 3 has deprecated support ofyield
based tests.Statements
yield
ing a simple function (callable) have been removed and a normal function call is included there.Statements
yield
ingassert_*
methods have been replaced with simpleassert
keywords as of now.Finally
--disable-pytest-warnings
has been removed.The goal of this PR is to eliminate all pytest warnings existing already.