Check with Mypyc level of strictness
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 20.6k
- Forks
- 3.3k
- PR merge metrics
- PR metrics pending
Description
Pitch
There's regular Mypy, and then there's strict Mypy. But even stricter than that is Mypyc. Mypyc is strictly stricter than strict Mypy -- everything accepted by Mypyc is accepted by strict Mypy, but not vice versa.
Currently, checking with the Mypyc level of strictness requires actually running Mypyc, and that means doing the code generation, which is slow.
It would be nice to be able to check with Mypyc level of strictness without doing all the code generation. Something along the lines of mypy --super-strict. Or maybe mypyc --check.
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
The issue names no files, tests, or entry points. Start by comparing the checks performed by regular strict Mypy and Mypyc, then determine how a check-only mode could reuse the stricter validation without code generation. Done means a command or option that reports Mypyc-level type errors without generating code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100