upstream type checking with a nightly version of `numpy`

Open
#11,371 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
numpy, python

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.

Description

CI topic-typing

#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

Dominant language
Python
Stars
4.2k
Forks
1.5k
Avg merge
2d 21h
Merged PRs (30d)
74

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from pydata/xarray

All issues in pydata/xarray

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.