Don't suppress typeshed warnings when using --custom-typeshed-dir
Open
Nobody has claimed this yet.
feature
needs discussion
priority-1-normal
topic-usability
- Dominant language
- Python
- Stars
- 20.6k
- Forks
- 3.3k
- PR merge metrics
- PR metrics pending
Description
When using --custom-typeshed-dir, I'm intentionally indicating that I'm using my own edited version of typeshed. It would be nice for typeshed warnings to be surfaced under these conditions.
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 at the handling of the --custom-typeshed-dir option and trace where typeshed warnings are suppressed. Add regression coverage for a custom edited typeshed and verify that its warnings are surfaced; done means the existing suppression no longer applies in this mode.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100