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

Suggestion: Implement Sourcery rules #11060

Open
diceroll123 opened this issue Apr 20, 2024 · 2 comments
Open

Suggestion: Implement Sourcery rules #11060

diceroll123 opened this issue Apr 20, 2024 · 2 comments

Comments

@diceroll123
Copy link
Contributor

Sourcery is a closed-source, paid program with refactoring/suggestion rules, some of which are covered by existing rules within Ruff.

Since Sourcery is closed-source, the rules would need to be clean room implementations.

Below, I've enumerated all current Sourcery rules with any overlap with Ruff 0.4.1, for Astral's consideration.

Note: There is of course the possibility that some unimplemented rules below are equivalent to different unimplemented rules from different libraries, such as Pylint.

I expect that any implementations made would fall under RUF (if there is no unimplemented alternative from another set of rules)?


@MithicSpirit
Copy link
Contributor

Do we know what license the Sourcery documentation is distributed under? There might be legal issues with basing implementations on it if it is sufficiently restrictive. Although, it might be fine regardless due to Google v. Oracle. I am not a lawyer; this is not legal advice.

@diceroll123
Copy link
Contributor Author

diceroll123 commented Apr 20, 2024

Also not a lawyer, but my intention here is the (surprisingly not the software development methodology of) clean room design.

After all, this issue's a proposal, and I would say nobody has the copyright over an idea of a lint rule, especially if we can't see the source to replicate it.

In any case, I leave it up to the team to decide!

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