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

Add Sphinx Lint to pre-commit #1786

Open
wants to merge 6 commits into
base: main
Choose a base branch
from
Open

Add Sphinx Lint to pre-commit #1786

wants to merge 6 commits into from

Conversation

hugovk
Copy link
Contributor

@hugovk hugovk commented Jan 14, 2025

Plus add a few other handy linters and bump GitHub Actions.


📚 Documentation preview 📚: https://python-packaging-user-guide--1786.org.readthedocs.build/en/1786/

Copy link
Member

@webknjaz webknjaz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It'd be nice to split this so it's obvious what triggered formatting..

@hugovk
Copy link
Contributor Author

hugovk commented Jan 14, 2025

Sure, how's this?

- repo: https://github.com/pre-commit/pygrep-hooks
rev: v1.10.0
hooks:
- id: rst-backticks
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is already mentioned below.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

BTW, I also tried this check, and it was horrible, because it complained about every instance of single-backticked words in my .rst files. It's valid to use single backticks, it's just not code.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, I've removed the duplicate.

Yep, it's valid, although it's pretty common people intend to write code but forget they're writing RST and not MD, and it shows as italics instead.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, also some projects explicitly define its role to be the same (https://github.com/pytest-dev/pytest/blob/517b006/doc/en/conf.py#L61C1-L61C25), confusing a casual contributor even more...

@@ -8,10 +8,11 @@ repos:
- id: check-added-large-files
- id: check-case-conflict
- id: check-merge-conflict
- id: check-symlinks
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What's the justification here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Flagged by the check-hooks-apply hook. Shall I remove check-hooks-apply and re-add check-symlinks?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Flagged by the check-hooks-apply hook:

Check hooks apply to the repository......................................Failed
- hook id: check-hooks-apply
- exit code: 1

check-symlinks does not apply to this repository

Shall I remove check-hooks-apply and re-add check-symlinks?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Honesty, not sure. I was just trying to understand how different bits of the PR might be related to the declared goal and each other...

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ned ended up not using this check: #1786 (comment). Perhaps, we shouldn't either.

@@ -8,10 +8,11 @@ repos:
- id: check-added-large-files
- id: check-case-conflict
- id: check-merge-conflict
- id: check-symlinks
- id: check-json
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you add explanation somewhere why one check replaces the other instead of being additional?

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll take a guess based on what I saw: check-hooks-apply complains that check-symlinks doesn't apply if the repo has no symlinks.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh.. I wish that was more apparent.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thinking about it... It's rather suboptimal: if we ever start having symlinks, they won't be checked after this patch because nobody will remember to re-add it.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree. But perhaps it means we don't want check-hooks-apply.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After trying it in coveragepy, I removed check-hooks-apply.

Comment on lines 51 to 54
- repo: meta
hooks:
- id: check-hooks-apply
- id: check-useless-excludes
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are these fast? If so, they should be closer to the beginning for responsiveness.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

On their own:

$ time pre-commit run --all-files
Check hooks apply to the repository......................................Passed
Check for useless excludes...............................................Passed
pre-commit run --all-files  0.23s user 0.07s system 95% cpu 0.315 total

Compared to another hook on its own:

$ time pre-commit run --all-files
rst ``code`` is two backticks............................................Passed
pre-commit run --all-files  0.15s user 0.05s system 71% cpu 0.283 total

The whole lot:

$ time pre-commit run --all-files
rst ``code`` is two backticks............................................Passed
check for added large files..............................................Passed
check for case conflicts.................................................Passed
check for merge conflicts................................................Passed
check json...............................................................Passed
check yaml...............................................................Passed
fix end of files.........................................................Passed
mixed line ending........................................................Passed
fix requirements.txt.....................................................Passed
trim trailing whitespace.................................................Passed
codespell................................................................Passed
Disallow improper capitalization.........................................Passed
rst ``code`` is two backticks............................................Passed
rst directives end with two colons.......................................Passed
rst ``inline code`` next to normal text..................................Passed
ruff.....................................................................Passed
ruff-format..............................................................Passed
Sphinx Lint..............................................................Passed
Check hooks apply to the repository......................................Passed
Check for useless excludes...............................................Passed
pre-commit run --all-files  4.24s user 1.08s system 276% cpu 1.923 total

The whole lot without them:

$ time pre-commit run --all-files
rst ``code`` is two backticks............................................Passed
check for added large files..............................................Passed
check for case conflicts.................................................Passed
check for merge conflicts................................................Passed
check json...............................................................Passed
check yaml...............................................................Passed
fix end of files.........................................................Passed
mixed line ending........................................................Passed
fix requirements.txt.....................................................Passed
trim trailing whitespace.................................................Passed
codespell................................................................Passed
Disallow improper capitalization.........................................Passed
rst ``code`` is two backticks............................................Passed
rst directives end with two colons.......................................Passed
rst ``inline code`` next to normal text..................................Passed
ruff.....................................................................Passed
ruff-format..............................................................Passed
Sphinx Lint..............................................................Passed
pre-commit run --all-files  3.98s user 1.02s system 300% cpu 1.666 total

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@hugovk

Tip

Pro tip: you can add -vv to pre-commit run and it will print out per-hook timings verbosely. It will be a bit more accurate.

But yeah, the idea here is that when the slower checks are running first, it may contribute to the feeling that it's stuck, while it's nicer the other way around. With that in mind, I'd probably put these at the beginning.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the tip!

time pre-commit run --all-files -vv
rst ``code`` is two backticks............................................Passed
- hook id: rst-backticks
- duration: 0.09s
check for added large files..............................................Passed
- hook id: check-added-large-files
- duration: 0.08s
check for case conflicts.................................................Passed
- hook id: check-case-conflict
- duration: 0.07s
check for merge conflicts................................................Passed
- hook id: check-merge-conflict
- duration: 0.06s
check json...............................................................Passed
- hook id: check-json
- duration: 0.02s
check yaml...............................................................Passed
- hook id: check-yaml
- duration: 0.05s
fix end of files.........................................................Passed
- hook id: end-of-file-fixer
- duration: 0.05s
mixed line ending........................................................Passed
- hook id: mixed-line-ending
- duration: 0.05s
fix requirements.txt.....................................................Passed
- hook id: requirements-txt-fixer
- duration: 0.02s
trim trailing whitespace.................................................Passed
- hook id: trailing-whitespace
- duration: 0.05s
codespell................................................................Passed
- hook id: codespell
- duration: 0.13s
Disallow improper capitalization.........................................Passed
- hook id: disallow-caps
- duration: 0.07s
rst ``code`` is two backticks............................................Passed
- hook id: rst-backticks
- duration: 0.06s
rst directives end with two colons.......................................Passed
- hook id: rst-directive-colons
- duration: 0.06s
rst ``inline code`` next to normal text..................................Passed
- hook id: rst-inline-touching-normal
- duration: 0.07s
ruff.....................................................................Passed
- hook id: ruff
- duration: 0.04s

All checks passed!

ruff-format..............................................................Passed
- hook id: ruff-format
- duration: 0.01s

2 files left unchanged

Sphinx Lint..............................................................Passed
- hook id: sphinx-lint
- duration: 0.3s

No problems found.

Check hooks apply to the repository......................................Passed
- hook id: check-hooks-apply
- duration: 0.09s
Check for useless excludes...............................................Passed
- hook id: check-useless-excludes
- duration: 0.08s
pre-commit run --all-files -vv  4.18s user 1.05s system 292% cpu 1.788 total

I've moved them to the beginning.

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

Successfully merging this pull request may close these issues.

3 participants