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 installation errors #170

Closed
DBvdHeijden opened this issue Apr 19, 2022 · 7 comments
Closed

pip installation errors #170

DBvdHeijden opened this issue Apr 19, 2022 · 7 comments

Comments

@DBvdHeijden
Copy link

Hi all!

When trying to install (either through pip or conda) I get an error with the numpy package (Failed building wheel for numpy). I saw this was an issue for someone else two months back, but don't really know how to solve this.. Any help would be much appreciated!

Thanks!

@mmckerns
Copy link
Member

I'm not seeing any build errors on any version of the supported python codes, platforms, and dependencies. What is your OS and version of python? What is your version of mystic and dependencies (e.g. numpy)?

@mmckerns
Copy link
Member

This sounds like it might be a duplicate of #164.

@DBvdHeijden
Copy link
Author

Hi! Thanks for the response - I thought I was running the latest version of python but apparently I was running 2.7 in my conda environment I see now (very dumb haha).. Will try to update to the latest version! Also, thank you for your work on mystic :)

@mmckerns
Copy link
Member

Ok. Let me know if you still have issues. By the way, python 2.7 is still supported, however support will be dropped this month (immediately after to the pending release is out).

@DBvdHeijden
Copy link
Author

So, I think I was running a newer version of python after all (3.9.7), but the command I used gave the python version the OS itself is running (I think?). I am running macOS Monterey (12.2.1) on a new M1 pro MacBook. My numpy version is 1.22.1 - any tips on what to do?

@mmckerns
Copy link
Member

mmckerns commented Apr 19, 2022

It sounds like this is a duplicate. This will be fixed with the next released mystic, which should happen in about a week or so. However, for a first attempt at a workaround, can you can try: pip install mystic --no-binary :all:...?

@mmckerns
Copy link
Member

I'm going to close this as a duplicate, but feel free to keep the thread going here until you have resolution. We can reopen it if it ends up not being a duplicate.

@mmckerns mmckerns added this to the mystic-0.3.9 milestone Apr 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants