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

Update Install Python in Mac Doc #382

Closed
jwokaty opened this issue Dec 12, 2023 · 2 comments · Fixed by #384
Closed

Update Install Python in Mac Doc #382

jwokaty opened this issue Dec 12, 2023 · 2 comments · Fixed by #384

Comments

@jwokaty
Copy link
Collaborator

jwokaty commented Dec 12, 2023

I don't think we need to brew install python anymore as described in https://github.com/Bioconductor/BBS/blob/devel/Doc/Prepare-macOS-Big-Sur-HOWTO.md#211-install-python-3 since tensorflow is now available for newer python versions, so this section in the documentation needs to be rewritten. Maybe it just needs to be a newer version or install the required dependencies (maybe we should also note what packages require them?). We should also put export PATH=/opt/R/x86_64/bin:$PATH or export PATH=/opt/R/arm64/bin:$PATH in /etc/profile.

Note that brew installing some packages, such as mono and salt may require a version of python to be brew installed and also openssl. In these cases, we should brew uninstall --ignore-dependencies $PACKAGE for the package (maybe brew autoremove too?). If brew install symlinks a brewed python, remove the link with brew unlink $PACKAGE.

Note: without a brewed openssl, it seems that pip3 will fail to update because it needs ssl, which is why we should use the default installed python instead.

On merida1, need to brew uninstall [email protected] and pip3 install dependencies since it is currently showing an ssl error visible at the end of pip3 list.

@hpages
Copy link
Contributor

hpages commented Dec 12, 2023

Yes please get rid of the brewed Python3. It's been a while since we don't need it anymore. See #182 (comment) (from August 2022).

If it comes back as the dependency of something else that we need to brew, and if the installation is "keg-only", then it should not be a problem because "keg-only" means that it won't be in the PATH. So hopefully we won't need to use brew uninstall --ignore-dependencies, which is something we should not use lightly and only as a very last resort.

We should also put export PATH=/opt/R/x86_64/bin:$PATH or export PATH=/opt/R/arm64/bin:$PATH in /etc/profile.

Is this related to Python? If not then maybe we can discuss this in a separate issue?

Thanks

@jwokaty
Copy link
Collaborator Author

jwokaty commented Dec 12, 2023

More related to #378, which is also related to this issue. I've put it there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants