Somehow pip install would do the right thing and hit my virtualenv, but pip list would rattle off Python 2.7 packages.įor Python, this is batting way beneath my expectations in terms of beginner-friendliness. Pip3 did not exist to start ( command not found) with and which pip would return /opt/local/Library/Frameworks/amework/Versions/2.7/bin/pip, the Apple Python.Īfter activation of the 3.6 virtualenv I wanted to work with, which python would return somepath/venv/bin/python It's a hack, but it works, and I know what it does: alias sudopip='sudo somepath/venv/bin/python somepath/venv/lib/python3.6/site-packages/pip/_main_.py' This didn't work so well when I had to do sudo pip as the root user doesn't know anything about my alias or the virtualenv, so I had to add an extra alias to handle this as well. alias pip='python somepath/venv/lib/python3.6/site-packages/pip/_main_.py' Conda packages include Python libraries (NumPy or matplotlib ), C libraries ( libjpeg ), and executables (like C compilers, and even the Python interpreter itself). Pip packages are Python libraries like NumPy or matplotlib. I dont know the difference between them, so I deliberately learned about it. The fundamental difference between pip and Conda packaging is what they put in packages. When you run PIP3, you can be sure that the module will be installed in Python 3. Your system will use one of your Python versions depending on what exactly is first in the system PATH variable. Given an activated Python 3.6 virtualenv in somepath/venv, the following aliases resolved the various issues on a macOS Sierra where pip insisted on pointing to Apple's 2.7 Python. After installing python3, I found that there are both pip and pip3 in the library. The difference between PIP and PIP3 in short and sweet: PIP is a soft link for a particular installer.
0 kommentar(er)
