bpo-42238: Doc CI: Disable suspicious checks. #26575
Merged
Conversation
They are slow and raise too many false positive, I'm in the slow process to try to change this.
|
LGTM. Maybe you can document this unknown command in the devguide? For example, near: |
JulienPalard
merged commit 227a093
into
python:main
12 checks passed
12 checks passed
bedevere/news
"skip news" label found
|
For the moment my biggest issue is: people are autonomously and quietly fixing what's reported by So my current idea is to let people people commit errors¹, fix them myself (I've setup a build bot to monitor this closely) to document true positives and try to implement them in 1: It is not expected to happen often, and have the nice side effet of not bothering people with false positives: 9 out of 12 errors reported by |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
They are slow and raise too many false positive, I'm in the slow
process to try to change this.
I've removed it from PEP 101 too to avoid the burden for RMs.
I've setup a cron to follow this closely / to avoid to forgot to monitor this closely.
https://bugs.python.org/issue42238