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. Many packages can also be installed via the setuptools extension or pip wrapper, see 5.4. 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 Installing Additional Python Packages There are several methods to install additional Python packages: Packages can be installed via the standard Python distutils mode (python setup.py install). 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. python3 points to Homebrews Python 3.y (if installed) pip3 points to. alias pip='python somepath/venv/lib/python3.6/site-packages/pip/_main_.py' Homebrew should work with any CPython and defaults to the macOS system Python. 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.

Install pip3 mac