resolving the nightly version of `numcodecs` fails
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4.2k
- Forks
- 1.4k
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 14
Description
On RTD, the nightly version of numcodecs currently fails to build, causing pixi's resolve step to fail (the package needs to be built when resolving to figure out the package version). I don't know why CI doesn't fail, but I can reproduce locally.
As for the reason, I'm not sure. The last passing build was ~11 days ago, which somewhat coincides with the release of cython=3.2.6, but this could also be a change in numpy.
cc @d-v-b, in case we can do anything in numcodecs to resolve this.
I guess we could work around this by moving the docs or nightly envs to a separate manifest (so at least on RTD we don't have to worry about that).
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
No file or test is named. Start by reproducing the nightly numcodecs failure locally during the pixi resolve step, then compare the effects of the cited Cython and NumPy changes and inspect the RTD and nightly environment manifests. Done means the affected environment resolves successfully on RTD, with the cause or a documented manifest workaround established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- numpy, python
- Domain
- build-system, documentation
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100