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
October 11, 2022 07:42
ezio-melotti
left a comment
There was a problem hiding this comment.
LGTM.
Does this need an entry in the 3.12 whatsnew?
Sorry, something went wrong.
vstinner
left a comment
There was a problem hiding this comment.
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?
Sorry, something went wrong.
|
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! |
Sorry, something went wrong.
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 |
Sorry, something went wrong.
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). |
Sorry, something went wrong.
The whatsnew also has a section for deprecated/removed APIs/modules/tools. See for example Lines 212 to 223 in e0ae9dd |
Sorry, something went wrong.
OK, so, why not :) |
Sorry, something went wrong.
Done. |
Sorry, something went wrong.
ezio-melotti
left a comment
There was a problem hiding this comment.
Thanks!
Sorry, something went wrong.
AA-Turner
left a comment
There was a problem hiding this comment.
Thanks @JulienPalard!
A
Sorry, something went wrong.
|
@JulienPalard, looks like the 3.11 and 3.10 branches still run |
Sorry, something went wrong.
I don't think that it's a good idea to backport. It's better to leave these stable branches as they are. |
Sorry, something went wrong.
|
That means that we will continue to get |
Sorry, something went wrong.
|
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 |
Sorry, something went wrong.
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! |
Sorry, something went wrong.
|
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). |
Sorry, something went wrong.
They have been replaced by
sphinx-lint.
closes gh-86404.