-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Drop isort 4, and clean up the resulting code
#10641
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
Conversation
isortisort 4, and clean up the resulting code
Pierre-Sassoulas
left a comment
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.
Great !
|
Forgot to remove one ignore, @Pierre-Sassoulas please review again 😅 |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #10641 +/- ##
==========================================
+ Coverage 95.94% 95.96% +0.02%
==========================================
Files 176 176
Lines 19519 19502 -17
==========================================
- Hits 18727 18715 -12
+ Misses 792 787 -5
🚀 New features to boost your workflow:
|
|
🤖 According to the primer, this change has no effect on the checked open source code. 🤖🎉 This comment was generated for commit 3c444d6 |
Type of Changes
Description
Due to #10637 I took an interest in our current dependency on
isort.Yesterday I made a new release for
isortwhichpylintshould just support so I bumped the version constraints.At the same time we should remove the more than 6 years old version, because it also doesn't know about the stdlib imports of newer Python versions that we do support.
This means we can simplify our code a bit, which should help if we ever decide to fully remove
isortor replace it.