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

Installing with Mac M1 #145

Open
yasmeenasali opened this issue Aug 2, 2023 · 4 comments
Open

Installing with Mac M1 #145

yasmeenasali opened this issue Aug 2, 2023 · 4 comments

Comments

@yasmeenasali
Copy link

I couldn't install from the environment.yml file on Mac M1, since theres no native build for python less than 3.8. I used the following workaround:

conda create -n kcwidrp
conda activate kcwidrp
conda config --env --set subdir osx-64
conda install python=3.7
conda env update --file environment.yml
pip install kcwidrp

It may be good to mention this in the documentation!

@caridlin
Copy link

I had the same issue installing on my Mac M1, and though

conda config --env --set subdir osx-64

was a workaround, it globally set the architecture to x86, which messed up with my other conda environments. I followed the answers here https://stackoverflow.com/questions/65415996/how-to-specify-the-architecture-or-platform-for-a-new-conda-environment-apple to modify the .zshrc file and installed Python 3.7 the following way

create_x86_conda_environment kcwidrp python=3.7

@ogtelford
Copy link

I had the same issue installing on my Mac M1, and though

conda config --env --set subdir osx-64

was a workaround, it globally set the architecture to x86, which messed up with my other conda environments. I followed the answers here https://stackoverflow.com/questions/65415996/how-to-specify-the-architecture-or-platform-for-a-new-conda-environment-apple to modify the .zshrc file and installed Python 3.7 the following way

create_x86_conda_environment kcwidrp python=3.7

I followed these instructions after encountering problems installing the DRP on an M2 MacBook Pro and this worked for me (thank you!) -- I agree, this would be a helpful addition to the documentation.

@prappleizer
Copy link

Just wanted to commend and add that it would be great if the pipeline could be tested and upreleased to at least python 3.8. 3.7 is already near EOL and the fact that this type of workaround is needed on two generations of computer says something... Python is on 3.12 right now and 3.7->3.8 wouldn't be a significant change to anything from the pipeline side (I'm pretty sure); see: astropy/astropy#15634 which fixes a setuptools issue that was happening if you try to install using newer python versions. (but really being 5 versions behind might motivate just getting it working on 3.11 to future proof it for a while...)

@vpicouet
Copy link

I tried to follow these steps without success on a mac M2.
python 3.7 was not available on Platform: osx-64 neither osx-arm64
Please let me know if there is another workaround.
Thanks!

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

5 participants