Auto generate pyright test config
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5.1k
- Forks
- 2.1k
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 82
Description
Take the information which stubs to exclude from the METADATA.toml files. On one hand this is necessary for #10722, i.e. to correctly handle requires_python, on the other hand this allows us to move a "stub incomplete" marker into the METADATA.toml file, and use it for other purposes than just the pyright tests. E.g. instead of relying solely on pyright to prevent regressions of "complete" stubs (which doesn't work great, since pyright doesn't understand Incomplete), we could have a separate script in CI.
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 inspecting the METADATA.toml files and the current pyright test configuration, then review the context in issue #10722. Done means the relevant stub-exclusion and incomplete-stub information is represented in METADATA.toml and can support pyright tests and other CI checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100