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

pip install collects latest (too new) numpy #776

Open
NoteboomM opened this issue Oct 3, 2024 · 0 comments
Open

pip install collects latest (too new) numpy #776

NoteboomM opened this issue Oct 3, 2024 · 0 comments
Assignees

Comments

@NoteboomM
Copy link

Problem description

I'm not too familiar with pip, but pip install pygimli appears to be pulling the wrong numpy - is it possible to change the requirement somewhere? It appears to require numpy>=1.25 which currently downloads/installs numpy v2.1.1 which doesn't work well with pyGIMLi at times. In contrast, conda install gimli::pygimli downloads/installs numpy v1.26.4

Your environment

--------------------------------------------------------------------------------
  Date: Thu Oct 03 14:22:21 2024 W. Europe Summer Time

                OS : Windows (10 10.0.22631 SP0 Multiprocessor Free)
            CPU(s) : 20
           Machine : AMD64
      Architecture : 64bit
       Environment : Python

  Python 3.10.15 | packaged by conda-forge | (main, Sep 30 2024, 17:41:41)
  [MSC v.1941 64 bit (AMD64)]

           pygimli : 1.5.2
            pgcore : 1.5.0
             numpy : 1.26.4
        matplotlib : 3.9.2
             scipy : 1.14.1
              tqdm : 4.66.5
           IPython : 8.28.0
            meshio : 5.3.5
            tetgen : 0.6.5
           pyvista : 0.44.1
--------------------------------------------------------------------------------

If I use the pip install in a new environment, it is the same, but with numpy: 2.1.1

Steps to reproduce

using pip install instead of a conda install

Expected behavior

Can the numpy requirement for the pip install be changed to a version range, or fixed to 1.26?

Actual behavior

If possible, please add one or more labels to your issue, e.g. if you expect that your issue is rather a question than a problem with the code, please add the label "question".

@carsten-forty2 carsten-forty2 self-assigned this Oct 3, 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

2 participants