Update config for breaking change in Tox 4.0.6 #150
Merged
Conversation
This file contains 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
tox-dev/tox#2676 for details. Signed-off-by: Rick Elrod <rick@elrod.me>
TheRealHaoLiu
approved these changes
Dec 12, 2022
relrod
added a commit
to relrod-EEs/awx-ee
that referenced
this pull request
Jan 17, 2023
tox-dev/tox#2676 for details. Signed-off-by: Rick Elrod <rick@elrod.me>
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.
tox-dev/tox#2676 for details.
Also tox-dev/tox#2658 and tox-dev/tox#2671
Signed-off-by: Rick Elrod rick@elrod.me
Effectively, Tox 4 changed this syntax (with no deprecation warning, no docs update other than an FAQ question). Tox 4.0.0 - 4.0.5 silently ate the error which is why we didn't see it, and 4.0.6 suddenly made it a fatal. 😬