Skip to content
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

Should python ruff fixer default to pass --no-fix on newer versions? #4719

Open
sirosen opened this issue Feb 6, 2024 · 0 comments
Open

Comments

@sirosen
Copy link

sirosen commented Feb 6, 2024

I recently had a lot of trouble figuring out how to configure ruff for use with ALE.
I found that the ruff linter was consistently failing with somewhat inscrutable messages.

It turned out that the default invocation pattern being used produces a fully fixed file as output under the latest ruff versions.

Adding --no-fix to the linter config fixed it, but I suspect that other users are struggling with this.
I might try to put together a PR for this at some point, but can't commit to that at present.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant