There are several other issues that can be found on this site. I think pip makes some simplifying assumptions about the the compilation environment. The different installs differ when you need more complex native libraries. The provision of venv and pipenv makes earlier answers less relevant as you now don't need a package manager, python now provides most of one. All installations of extra modules are done using pip and you can deal with different versions of python with venv. It took me quite sometimes to figure out that.įor pure python it probably does not matter. But to my surprise my system python is still the one installed by httpie. For example I installed httpie and uninstalled it. I do find brew has an "annoying" feature, when brew’s Python being installed as a dependency for a bottle and then I uninstall the bottle, the brew's Python remains. But since PATH is modified by the installer or brew (brew puts /usr/local/bin before /usr/bin) so preinstall python is shadowed. MacOS preinstall python at /usr/bin/python & /usr/bin/python3 which remain unchanged. `python3`, `python3-config`, `pip3` etc., respectively, have been installed into Unversioned symlinks `python`, `python-config`, `pip` etc. Sometimes I don't run brew install python directly but install some bottle, which installs python, e.g brew install httpie will install python, then brew complains if I then install python thru brew, brew will complain. /./Library/Frameworks/amework/Versions/3.9/bin/python3 PATH="/Library/Frameworks/amework/Versions/3.8/bin:$" zprofile like following and create softlink /usr/local/bin/python3
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |