-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
CI/TST: pip extras install #49241
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
CI/TST: pip extras install #49241
Conversation
blosc on pypi has a lower version than on conda-forge. Pending to see if blosc will be updated on pypi: Blosc/python-blosc#297 EDIT: Updated the OP to note that |
Co-authored-by: JMBurley <[email protected]>
Co-authored-by: JMBurley <[email protected]>
…into tst/pip_extras
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This blocks quite a few runners for significant minutes (around 15 per build). Is there a way to avoid building pandas all the time?
Looks like |
@phofl found a hacky workaround to not build the extensions and now the jobs complete in a few seconds. Open to better ideas on how to achieve the same thing. |
This works consistently? I'd be ok with this for the time being. Alternative would be to change setup.py directly, correct? |
Yeah this worked when I tried in in 05b6ef7.
Yeah I think so, but my attempts at this were not successful. I tried creating a |
Thanks, lets try the current solution and adjust if necessary |
@mroeschke I'm not sure if this is adding anything useful to the test matrix. Taking a quick look, this just tests that installing each of the extras works(this is already covered by environment.yml/requirements-dev.txt, since all dependencies are installed when we install from there and these deps are just a subset of thoe), not that the extras are correct. (IMO, you'd need some sort of "golden" file to check this). There's also coverage for this in the pre-commit checks which should be enough IMO. So if it's fine with you, I would propose reverting this PR, since it relies on a setuptools hack that is blocking my meson PR. |
Not really, this checks that pip install pandas[foo] works, this is different than the environment yml. |
Yeah I think there still some use here smoke testing One concern here was build speed since most of the time was built the cython extensions, but I suppose we can live with some extra build time for now and remove my hack (modifying setup.py in the job) which should unblock your meson PR. Alternatively do you have any ideas on how to disable building cython extensions when pip installing? |
Since it's a subset, if we know installing all the dependencies works, then installing only some of them should work too, right?
I came across a rejected issue pypa/pip#4783. It doesn't seem like it. Why don't we restrict these builds to PRs tagged with "Build" for now? That should be a good compromise. |
Sure that would be fine with me |
(c-)blosc
is only available on conda, so removing it from the pip extrashttps://www.pytables.org/usersguide/installation.html#prerequisites