Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork32.1k
bpo-42238: Doc CI: Disable suspicious checks.#26575
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
They are slow and raise too many false positive, I'm in the slowprocess to try to change this.
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.
Maybe you can document this unknown command in the devguide? For example, near:
https://devguide.python.org/documenting/#gotchas
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 |
bedevere-bot commentedOct 12, 2022
GH-98221 is a backport of this pull request to the3.10 branch. |
Uh oh!
There was an error while loading.Please reload this page.
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