Pin isort version to 4.x due to big changes in 5.x #6
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
Codecov Report
@@ Coverage Diff @@
## master #6 +/- ##
=======================================
Coverage 95.28% 95.28%
=======================================
Files 1 1
Lines 382 382
=======================================
Hits 364 364
Misses 18 18 Continue to review full report at Codecov.
|
tlambert03
approved these changes
Jul 7, 2020
|
thanks for catching! |
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.
isort 5.0 both makes backwards-incompatible changes to the Python API and stops sorting and de-duplicating imports across blocks. I created an
isort-5branch to just update to the new API, but then I realized the codegen output didn't look as nice. Maybe a minor issue, but you can decide which approach you prefer!