-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Codespell fixes #10947
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
Codespell fixes #10947
Conversation
|
Now the execution of codespell starts, but it seems codespell itself crashes: |
|
Now that really is an upstream issue. We can update the codespell hook in |
|
This was easy to fix: codespell-project/codespell#2520 |
|
Ah, because Python's |
|
I guess this is the case. I copied this line from another function in this file. This line was the only open statement which didn't specify the encoding. Regarding this PR, I confirm, that it fixes codespell execution under Windows! |
|
Codespell 2.2.2 is released, with my bugfix merged: https://github.com/codespell-project/codespell/releases/tag/v2.2.2 |
|
89d8611 to
3b1642e
Compare
|
The pre-commit issue is expected because the spelling fixes touch a lot of files, including files that have formatting issues. Merge? |
daschuer
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.
Yes, Thank you.
There are some more findings. But that does not matter.
Attempt to solve #10946 by getting rid of the custom codespell wrapper, which not only makes pre-commit hard to use on windows, it's also broken (
pre-commit run codespell --all-filesdoes not work). Pre-commit failues are expected and should be ignored, because this touches a lot of files.@JoergAtGithub please check if
pre-commit run codespell --all-filesworks when you have this branch checked out.