-
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
[WIP] Refactor test_memory.py as per pytest design. #460
Conversation
46cb313
to
56c1fb5
Compare
I would rather have topic-based PRs rather than file-based PRs. It does help the review process a lot by focusing on one aspect at a time. In this particular case having a PR that just removes all the Once this is done, remember to remove disable-warnings from setup.cfg. |
@lesteve This includes only tests of test_memory.py ? Because there are still 112 pytest warnings undone, and |
When I say all the tests I meant all the tests from all the files.
Do you have an example? Technically I do not think they require All I am trying to say is that I would do it in this order:
|
I am keeping this PR on a hold for a while, not doing |
Thanks for trying to keep the github tracker tidy! Keeping the PR open would have been fine too, to be perfectly honest. |
@lesteve yeah the tracker remains clean, plus I do this because if a third person comes here, he may get a clue that the PR was closed due to a change of plan and reopened later for a related task 😁 |
Rebasing / force pushing does not allow this PR to be reopened, I will make a separate one. |
Third Phase PR on #411 (Succeeding PR #458)
NOTE: Rebasing / force pushig didn't allow reopening of this PR, hence a new PR has been created as a replacement ( #466 )