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

We should remove oldest-supported-numpy whenever it is seen #553

Open
marcelotrevisani opened this issue Aug 20, 2024 · 0 comments
Open

Comments

@marcelotrevisani
Copy link
Member

          We should remove `oldest-supported-numpy` whenever it is seen. That's used by wheels specifically to [configure builds with specific `numpy` versions]( https://github.com/scipy/oldest-supported-numpy/blob/23ece5a161d5957f5142991393d2ae689ee45b9d/setup.cfg#L17 ) (not sure why a wheel would use `oldest-supported-numpy` at runtime unless they are some kind of build tool)

In any event it doesn't make sense in the Conda case where we configure NumPy versions used in some conda_build_config.yaml or other variants

On the Conda side, we need only add numpy (unconstrained) to requirements/host and copy over any dependencies value of numpy to requirements/run

Originally posted by @jakirkham in #552 (comment)

@jakirkham jakirkham mentioned this issue Aug 20, 2024
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

No branches or pull requests

1 participant