Skip to content

BLD/DEV/CI: better Pixi setup#920

Merged
hameerabbasi merged 12 commits intopydata:mainfrom
lucascolley:pixi
Feb 2, 2026
Merged

BLD/DEV/CI: better Pixi setup#920
hameerabbasi merged 12 commits intopydata:mainfrom
lucascolley:pixi

Conversation

@lucascolley
Copy link
Collaborator

@hameerabbasi are you open to taking on changes in this vein to move to pixi-build and make environments conda-forge-based? I would like to use sparse from source with SciPy if I go ahead with the coo_array support, and this will make that a lot easier.

@lucascolley lucascolley marked this pull request as draft January 29, 2026 11:25
@codspeed-hq
Copy link

codspeed-hq bot commented Jan 29, 2026

CodSpeed Performance Report

Merging this PR will not alter performance

Comparing lucascolley:pixi (b98cdff) with main (5e5f0fd)

Summary

✅ 340 untouched benchmarks

@lucascolley
Copy link
Collaborator Author

is this a known issue @hameerabbasi ?

  /home/runner/work/sparse/sparse/.pixi/envs/finch/lib/python3.13/site-packages/finch/tensor.py:9: DeprecationWarning: numpy.core.numeric is deprecated and has been renamed to numpy._core.numeric. The numpy._core namespace contains private NumPy internals and its use is discouraged, as NumPy internals can change without warning in any release. In practice, most real-world usage of numpy.core is to access functionality in the public NumPy API. If that is the case, use the public NumPy API. If not, you are using NumPy internals. If you would still like to access an internal attribute, use numpy._core.numeric.normalize_axis_tuple.

@hameerabbasi
Copy link
Collaborator

I forgot to hit the submit button on the review. 😅

@hameerabbasi
Copy link
Collaborator

is this a known issue @hameerabbasi ?

/home/runner/work/sparse/sparse/.pixi/envs/finch/lib/python3.13/site-packages/finch/tensor.py:9: DeprecationWarning: numpy.core.numeric is deprecated and has been renamed to numpy._core.numeric. The numpy._core namespace contains private NumPy internals and its use is discouraged, as NumPy internals can change without warning in any release. In practice, most real-world usage of numpy.core is to access functionality in the public NumPy API. If that is the case, use the public NumPy API. If not, you are using NumPy internals. If you would still like to access an internal attribute, use numpy._core.numeric.normalize_axis_tuple.

It shouldn't be causing a hard failure; should it? It's been known for a while.

@lucascolley
Copy link
Collaborator Author

if this looks good I can proceed with converting the rest of CI

@hameerabbasi
Copy link
Collaborator

Looks good. Would you like to do it in this PR or another one?

@lucascolley lucascolley marked this pull request as ready for review February 2, 2026 19:09
@lucascolley
Copy link
Collaborator Author

would be great if we can merge this already I suppose!

@lucascolley lucascolley changed the title WIP: better Pixi setup BLD/DEV: better Pixi setup Feb 2, 2026
@lucascolley lucascolley changed the title BLD/DEV: better Pixi setup BLD/DEV/CI: better Pixi setup Feb 2, 2026
@hameerabbasi hameerabbasi merged commit 352fc98 into pydata:main Feb 2, 2026
17 of 19 checks passed
@hameerabbasi
Copy link
Collaborator

Thanks! I'll need to edit the list of required jobs for the upcoming PRs.

@lucascolley
Copy link
Collaborator Author

thanks Hameer :)

@lucascolley lucascolley deleted the pixi branch February 2, 2026 19:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants