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

[Question] A status page for all implemented plugins and rules? #9354

Open
mikaelarguedas opened this issue Jan 2, 2024 · 1 comment
Open

Comments

@mikaelarguedas
Copy link
Contributor

mikaelarguedas commented Jan 2, 2024

Hey there 👋

Thanks for this great project!

I'm exploring the idea of migrating some projects from flake8 to ruff.
I'm currently having a hard time seeing exactly all the flake8 rules I rely on v.s. the ones implemented in ruff.

Apologies if this is the wrong venue for this or duplicating lots of existing discussions on that topic... happy to be redirected to the right place

My current approach:

  • for each flake8 plugin I use, find the relevant section in the ruff rules
    • side-by-side compare the rules provided by the latest version of the coresponding flake8 plugin
    • for the missing ones flag them to check later in ruff issues or other existing ruff rules if they are: already covered by other ruff rules, obsolete and wont be implemented, to be implemented

The process seems tedious, manual and error prone.
Is there a central place where one can find:

  • a side by side comparison of flake8-plugin behavior (at a given version) and ruff rules
    • for the ones not implemented: a status or rationale

This would help a lot figuring out how ruff would behave compared to a given flake8 set of plugins / versions for a given project and also update the list of rules to be implemented when new versions of plugins come out.

Thanks!

@akx
Copy link
Contributor

akx commented Jan 5, 2024

I've been thinking of implementing something like this to (try to) cover all of the reimplemented rules, but by golly do I have too many side projects...

For context (and prior art),

  • my pylint-to-ruff project currently parses the list from the issue Implement Pylint #970 and hopes for the best
  • I think flake8-to-ruff just relies on its own tribal knowledge (since it's built from this repo afaiu), etc. (It might be a good idea to port it to Python instead?) was retired in Remove flake8-to-ruff #9329, so it might be worth to reimplement it in Python as a separate project that'd use this same knowledge.

It would certainly be useful if all of this was in one machine-readable place 😄

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

No branches or pull requests

2 participants