Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

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

Merged

Conversation

JulienPalard
Copy link
Member

@JulienPalardJulienPalard commentedJun 7, 2021
edited by bedevere-bot
Loading

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

They are slow and raise too many false positive, I'm in the slowprocess to try to change this.
Copy link
Member

@vstinnervstinner left a 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

@JulienPalardJulienPalard merged commit227a093 intopython:mainJun 8, 2021
@JulienPalardJulienPalard deleted the mdk/drop-suspicious branchJune 8, 2021 07:23
@JulienPalard
Copy link
MemberAuthor

For the moment my biggest issue is: people are autonomously and quietly fixing what's reported bymake suspicious, so I don't have a list of true positives to work on.

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 inmake check (or in Sphinx).

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 bymake suspicious are false positives.

@bedevere-bot
Copy link

GH-98221 is a backport of this pull request to the3.10 branch.

JulienPalard added a commit that referenced this pull requestOct 12, 2022
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@vstinnervstinnervstinner approved these changes

Assignees
No one assigned
Labels
docsDocumentation in the Doc dirskip news
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

4 participants
@JulienPalard@bedevere-bot@vstinner@the-knights-who-say-ni

[8]ページ先頭

©2009-2025 Movatter.jp