-
-
Notifications
You must be signed in to change notification settings - Fork 31.4k
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
gh-86404: Doc: Drop now unused make suspicious and rstlint. #98179
Conversation
They have been replaced by [sphinx-lint](https://github.com/sphinx-contrib/sphinx-lint). closes pythongh-86404.
64192cb
to
dc5cf61
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Does this need an entry in the 3.12 whatsnew?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. sphinx-lint is a great success!
It's good that Doc/tools/susp-ignored.csv
can be removed. It can be removed because sphinx-lint has less false positives, right?
It seems like
cc @pablogsal @Yhg1s sphinx-lint is run by the "Docs / Docs" CI job on this PR: "Check documentation" step:
In short, sphinx-lint is now run on all documentation changes, not only late during releases. Issues are catched earlier: good! |
I don't think so as it's not a new thing, it's an old thing being cleared (it was a tool to help migration from LaTeX documentation to Sphinx documentation, so its removal is long overdue). It's been one year that the CI no longer uses |
This list of repositories are automatically checked by sphinx-lint CI to "guarantee" no false positive are introduced as release time, like it happened a few days ago with the "default-role debacle" (which happened because this checker is not enabled by default, to it went under the radar, it's fixed now, we test each repos with their real set of checkers). The goal is to stick to 0 false positive (aiming at the impossible... because why not). |
The whatsnew also has a section for deprecated/removed APIs/modules/tools. See for example Lines 212 to 223 in e0ae9dd
|
OK, so, why not :) |
Done. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @JulienPalard!
A
@JulienPalard, looks like the 3.11 and 3.10 branches still run |
I don't think that it's a good idea to backport. It's better to leave these stable branches as they are. |
That means that we will continue to get |
3.11 isn't running it anymore, since it got removed here: 3.10 however is still running it. If this is a problem we could just switch to |
Thanks, that makes sense! I think I remember seeing some false positives recently on some backports — they must have been backports to 3.10. Agreed that backports should also be as minimal as possible! |
I propose just disabling I don't feel the need to add sphinx-lint there: the PR will come from main, where they have already been checked, and as victor says, better not touch those stable branches too much (I mean let's remove pain, not add some). |
They have been replaced by
sphinx-lint.
closes gh-86404.