-
-
Notifications
You must be signed in to change notification settings - Fork 584
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
Crash on pylint's functional test with a bogus encoding declared #1487
Comments
@Pierre-Sassoulas thanks for forwarding this issue along! I'm thinking it might make sense for isort to: Thanks! |
Thank you for the quick reply. This sound good, I think the main thing to consider is not blocking a batch treatment, I think that you could have the same behavior for a single file to make your life easier. |
Opened a PR #1496 trying to solve this issue. Its not complete and not clearing all the tests, have a look and help me out :) Thanks |
Update: this has just been released to PyPI in 5.6.0 release of isort: https://pycqa.github.io/isort/CHANGELOG/#560-october-7-2020 Thanks! ~Timothy |
Thanks for the update, and congrats on the fast fix :) ! |
This is voluntarily a hard case to handle, here's the file : https://github.com/PyCQA/pylint/blob/master/tests/functional/u/unknown_encoding_py29.py
I don't think if isort should do anything about it, except exiting gracefully instead.
The text was updated successfully, but these errors were encountered: