chore(core): pin pytest to 7.1.3#690
Closed
bringhurst wants to merge 1 commit intopython-zk:masterfrom
Closed
Conversation
pytest removed their dependency on py in: pytest-dev/pytest@19dda7c This change pins pytest to 7.1.3 until a path forward is chosen.
942c238 to
d40e495
Compare
Contributor
Author
|
Closing this. Although this is a problem -- the real issue I was seeing is that tox-wheel is deprecated and doesn't work with tox 4. See #691 instead. |
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
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.
Why is this needed?
This change is intended to avoid errors like the following at build (tox) time:
pytest removed the dependency on py in:
pytest-dev/pytest@19dda7c
This change pins the version of pytest to one that includes py until a path forward can be agreed on (e.g. include py explicitly or via a transitive dependency).
Proposed Changes
Does this PR introduce any breaking change?
No. This change affects build/test only.