Replies: 3 comments 3 replies
-
tool.ruff.select contents:
tool.ruff.lint.select contents:
|
Beta Was this translation helpful? Give feedback.
0 replies
-
tool.ruff.ignore contents:
tool.ruff.lint.ignore contents:
|
Beta Was this translation helpful? Give feedback.
0 replies
-
@henryiii -- This is really cool... I'm independently curious what the distribution of build backends looks like (inspired by https://twitter.com/mitsuhiko/status/1754282328736559223, which led me to think we could scrape PyPI to get a quantitative answer, which led me to recall that you'd already done it). |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I've been analyzing all pyproject.toml's, and thought I'd look at
tool.ruff
. I can answer various questions, but I thought I'd look at histograms of a few interesting things. A few quick stats:I haven't checked file info, but I do have all the metadata for every file, so I could check the numbers of ruff.toml's/.ruff.toml's (though anyone could, the only slow/hard part is downloading file contents)..ruff.toml
's and 84ruff.toml
s, selecting on distinct projects. A project might not include these files in an SDist, though, while pyproject.toml should always be present (same thing when checking.pre-commit-config.yaml
, which had 7,724 instances).tool.ruff contents:
tool.ruff.lint contents:
A few projects set
tool.ruff.format
directly to a string, which breaks my analysis of it's contents at the moment.I can run queries if anyone is curious about anything. Or the dataset (pyproject.toml's), which is about 30MB as a
.parquet
file.Beta Was this translation helpful? Give feedback.
All reactions