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

Installation fails due to conflicting numpy version #4

Open
NeolithEra opened this issue Dec 11, 2019 · 1 comment
Open

Installation fails due to conflicting numpy version #4

NeolithEra opened this issue Dec 11, 2019 · 1 comment

Comments

@NeolithEra
Copy link

Hi, users are unable to run musco-pytorch due to dependency conflict with numpy package. As shown in the following full dependency graph of musco-pytorch, musco-pytorch requires numpy *,while scikit-tensor-py3 requires numpy ==1.16.*.

According to pip’s “first found wins” installation strategy, numpy 1.17.4 is the actually installed version. However, numpy 1.17.4 does not satisfy ==1.16.*.

Dependency tree-----------

musco-pytorch - 1.0.3
| +- absl-py(install version:0.8.1 version range:*)
| +- flopco-pytorch(install version:0.1.3 version range:*)
| +- numpy(install version:1.17.4 version range:*)
| +- scikit-tensor-py3(install version:0.4.1 version range:*)
| | +- numpy(install version:1.16.5 version range:==1.16.*)
| | +- scipy(install version:1.3.3 version range:==1.3.)
| +- scipy(install version:1.3.3 version range:*)
| +- tensorly-musco(install version:0.4.5 version range:*)

Thanks for your help.
Best,
Neolith

@NeolithEra
Copy link
Author

Suggested Solution

  1. Fix your direct dependency to be numpy <1.17.0. I have checked this revision will not affect your downstream projects now.
  2. Ask your upstream project scikit-tensor-py3 to loose the version range of numpy.
  3. Remove your direct dependency numpy, and use numpy transitively introduced by scikit-tensor-py3.

@juliagusak Which solution do you prefer, 1, 2 or 3?
Please let me know your choice. I can submit a PR to solve this issue.

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