[engsys] fix: Broken next-pylint tox environment#30526
Closed
kdestin wants to merge 1 commit intoAzure:mainfrom
Closed
[engsys] fix: Broken next-pylint tox environment#30526kdestin wants to merge 1 commit intoAzure:mainfrom
next-pylint tox environment#30526kdestin wants to merge 1 commit intoAzure:mainfrom
Conversation
Member
Author
|
This had already been fixed by #30515 |
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.
Description
This PR is a follow up to #30159, and fixes the
next-pylinttox environment which was broken by that PRcc: @scbedd , @l0lawrence
Background
#30159 includes df6b428 which was an attempt to better document the tox environments defined in tox.ini
The commit accidentally removed the
pylint==frompylint==2.15.8(see df6b428#diff-046db483898138bdccf106f32155fe12e3658ff0dd64ff0968507e3ffe15d09bL104-R107 ), which causes installation of pylint to fail.
All SDK Contribution checklist:
General Guidelines and Best Practices
Testing Guidelines