TST/MNT: deprecate unused fixture#20795
Merged
Merged
Conversation
tacaswell
added
the
API: changes
This is left over from an early pass at nose -> pytest conversion
tacaswell
force-pushed
the
mnt_deprecate_unused_fixture
branch
from
febcaad to
8385d46
Compare
timhoffm
approved these changes
Aug 5, 2021
Member
Author
|
I found this while trying to debug the coverage decrease in #19255 |
QuLogic
approved these changes
Aug 6, 2021
Member
|
The deprecation says 3.5, but the milestone says 3.6? |
Member
Author
User error on my part in milestoning 🐑 |
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
4 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.
This is left over from an early pass at nose -> pytest conversion
PR Summary
PR Checklist
pytestpasses).flake8on changed files to check).flake8-docstringsand runflake8 --docstring-convention=all).doc/users/next_whats_new/(follow instructions in README.rst there).doc/api/next_api_changes/(follow instructions in README.rst there).