Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Warn about unused `noqa`s

Open
#454 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
tooling

Research direction

Start by reproducing the configuration described in the issue: mark ASYNC as external and add an unnecessary noqa. Read the documentation section covering external checks and noqa handling, then trace the relevant linter entry point. Done means the configuration still works while an unnecessary noqa is reported, with tests covering the behavior.

Written by the indexing model from the issue text.

Description

new rule

Following the advice in the docs, I marked ASYNC as external to ruff. This also means I don't get warned about unnecessary noqas, unless I'm missing something. It's possible the docs describe how to avoid this! I didn't really read them.

Dominant language
Python
Stars
26
Forks
10
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from python-trio/flake8-async

All issues in python-trio/flake8-async

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.