-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Disallow isort 5.13.0 #9290
Disallow isort 5.13.0 #9290
Conversation
For instance, in astroid, |
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.
This is only for our tests right? That probably shouldn't leak to our dependencies as the tool itself still works?
Well, one of the tests indicates runtime behavior changes in astroid, which is critical to pylint. So no, I don't think it's a matter of tests only. |
It's possible that 'yarg' is patching sys.path, which makes me nervous. |
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.
Sorry, missed that test! The others looked fine. Indeed, let's not allow this.
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.
LGTM.
Long term for this part of the code I thought about:
- use ruff instead of isort internally ?
- an optional dependency for isort/ruff like the one we have for spelling,
- dump the check and tell user to use isort/ruff directly ?
But of course fixing astroid is an option 😄
baby steps! 👶 🩰 |
Refs #9270 (cherry picked from commit 47410ad) Co-authored-by: Jacob Walls <[email protected]>
Refs #9270
isort
5.13.0 pulls in many dev dependencies as runtime dependencies, some of which cause behavior differences in astroid. See logs.Refs PyCQA/isort#2206