upstream type checking with a nightly version of `numpy`
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4.2k
- Forks
- 1.4k
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 14
Description
#11370 has the side-effect of not installing the nightly version of numpy into the typing env. I went ahead and merged that PR to resolve a bunch of other issues, but we'll have to figure out what to do about this.
For context, pixi / uv are much stricter in keeping installed versions compliant, and scipy-stubs depends on a specific range of optype[numpy], which in turn depends on a specific range of python versions, which excludes the current dev versions of numpy.
cc @Illviljan, @headtr1ck
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 reviewing #11370 and the typing environment configuration, then reproduce dependency resolution with pixi or uv. Check how scipy-stubs and optype constrain Python and numpy versions; done means the typing environment can install and use a nightly numpy version without violating those constraints.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- numpy, python
- Domain
- build-system, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100