Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change one CI job to use an editable install #26337

Closed
rgommers opened this issue Apr 23, 2024 · 0 comments · Fixed by #26655
Closed

Change one CI job to use an editable install #26337

rgommers opened this issue Apr 23, 2024 · 0 comments · Fixed by #26655

Comments

@rgommers
Copy link
Member

This is a follow-up to gh-26325, which fixed the test suite so it passes (at least on a regular Linux numpy-dev env) with an editable install:

$ pip install -e . --no-build-isolation
$ pytest numpy

This is not tested at all in CI at the moment, so it's fairly easily broken again. We should pick a suitable existing job and change it to use an editable install rather than spin or a regular install via a wheel. In case there's no suitable job, we can add a new one - but that's probably not necessary. Just need a generic Linux one for which compile tests (which don't work with editable installs) aren't important.

JuliaPoo added a commit to JuliaPoo/numpy that referenced this issue Jun 10, 2024
See numpy#26337. As suggested by Ralf the `full` job in `linux.yaml` was
modified to run an editable install.
rgommers pushed a commit that referenced this issue Jun 10, 2024
Closes gh-26337. As suggested by Ralf the `full` job in `linux.yml` was
modified to run an editable install.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant