python-trio / python-trio/flake8-async
Warn about unused `noqa`s
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 26
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
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.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100