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.
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
Update fixate-requirements.py to cope with PIP 20.3.3 #5123
Update fixate-requirements.py to cope with PIP 20.3.3 #5123
Changes from 27 commits
82d774c
ab3bc0c
9e7a23f
b71eec3
16432b0
1948b0b
7d8e511
95a893b
034408a
143523d
e1cdd3d
ddf0f38
bad16d6
cfe51d3
72b4091
56c2b3a
128d385
2094ca8
e94913a
3ed3841
b2bcfac
9093213
aa2d4ec
fff7b5a
9d9fbcf
f2fa7e7
65473c1
eb40242
5fd8392
c15d75b
ddfc8aa
40dda02
636e2d5
6cccab9
4efc99a
dfa17d0
ee0fa53
1c435b2
c7248c4
2b064a4
53622b9
2814730
b201768
686c14a
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Was there a reason you pinned this to <5.0.0?
According to the changelog for
isort
v5.0.0:Which should be fine for this repo now.
If we do need to keep it pinned to <5.0.0, that would also work fine, but I'd like to start documenting why we pin certain packages to certain versions.
If we keep that pinned to a maximum version, it potentially complicates our life in the future with pylint:
StackStorm/st2-rbac-backend#46 is being held up by this PR due to this, which is not a big deal, it just forces a resolution order as we slowly crawl towards the next major ST2 release.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@blag I copied the version that was in st2-auth-ldap that was needed to get the CI working on st2-auth-ldap. And I believe that requirement was for pylint 2.6.0.
BUT that's a bit odd that the same pylint is now saying < 6 not < 5.
I was also seeing the new pip complain if you have one requirement saying packageA >=4.2.5 and packageB say >=4.25 and < 6. I will see if I can get it to pass with isort > 4.2.5, but I think with the new pip that will complain. But I'll double-check in case it was something else.