Homebrew's migration to python 3.9 is unnecessary and too forceful #105
-
Hi, just a note that this homebrew migration (Homebrew/homebrew-core#62201) completely broke my mac system. I wanted to grab a particular package (asciinema) which has a python 3.8 variation for the python 3.8 i have via homebrew. Getting asciinema remove all my other python (including 3.8) which left all my virtual environments dangling and threw python 3.9 on my system, which many python packages don't support yet... (e.g. jax, tensorflow, etc...) -- so even if it's out, I don't understand why we're forcing the upgrade... Is there a way to not force users to uproot their entire python? I've got a lot of |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
To fix this, I'm doing
inside |
Beta Was this translation helpful? Give feedback.
-
Homebrew is an evergreen package manager and will update to the latest version of dependencies whenever it can. |
Beta Was this translation helpful? Give feedback.
To fix this, I'm doing
inside
/usr/local/Homebrew/Library/Taps/homebrew/homebrew-core
and then I'm reinstalling viaHOMEBREW_NO_AUTO_UPDATE=1 brew install python3
to fix everything up.