-
-
Notifications
You must be signed in to change notification settings - Fork 70
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
setup on M1 Mac #154
Comments
IIRC, python 3.9 is required for M1 support. haven't tried 3.8. however, even with 3.9 i ran into a lot of conda dependency issues with the miniforge installer for the M1. it could handle dependencies, but not dependencies of dependencies. haven't had a chance to loop back to see if there's since been a fix for that. |
If there is willingness to try a few things:
For the workshop, we might have to make a separate set of instructions for M1; and we can have a Binder instance as a fallback. We could have troubleshooting at the Astropy booth the week after the workshop. |
This is not true. What probably happens is that you are trying to install a |
that sounds like a good explanation for the root cause of what i saw. i was able to get everything installed eventually by installing the deep dependencies manually and then working upward from there. so everything i needed was built for in the meantime, i stick with my strong recommendation that users run astropy and the rest of the scientific python stack under rosetta until apple silicon is officially supported by the default conda and pip channels. |
What has worked. I did it line-by-line:
And now only two things left which failed to import when I ran
PROGRESS! I will start digging into how to get the utils packages installed but any hand holding advice is welcome. |
I got more things to work! Just going to edit the above comment. |
Now i'm running into this error when I try
I get this same error with another package I'm working on so at least there's consistency! |
@kelle Those warnings are coming from trying to build |
@kelle If indeed |
@larrybradley , might be easier to chat on slack? As far as I can tell, numpy is indeed installed.
|
yeah, if you can't install |
the other packages i needed to install from source ran into the same problem when installing via |
cloned photutils and then ran |
Yep, that worked (I used
|
I've put this workflow in the Google Doc Setup for M1 Mac for Scientific Astro Programming. And I think we can close this issue. :) |
uh-oh, I think we forgot to add ccdproc to the workshop installation instructions! I see it in the Google doc, so does that mean you've installed it already? |
I'm trying to get setup on a new ARM mac and I've hit this problem when trying to create the new environment using the yml file. I've followed this document so far. I'm looping in @tepickering since he helped me get this point.
The text was updated successfully, but these errors were encountered: