PIP and the user directory

Article title*

Article revisions must have a non-empty title

Article body*

This is a quick note about python + pip best practices: ***never use sudo pip!*** It creates files only readable by root and breaks your python install.

Instead, always run pip install with --user:

# E.g.
    pip install --user <package>

# Or
    /path/to/specific/python -m pip install --user <package>

After installing packages, python should already be searching the user director as part of [`sys.path`](https://bic-berkeley.github.io/psych-214-fall-2016/sys_path.html).

Related error from not doing this: [stackoverflow.com: ImportError: No module named virtualenv](https://stackoverflow.com/a/40352303/1888983)

What's the difference? [stackoverflow.com: sudo pip install VS pip install --user](https://stackoverflow.com/questions/29310688/sudo-pip-install-vs-pip-install-user)

Also, versioned dependencies is a nightmare and not installing random packages system wide is a good thing. Using virtualenv and alternatives is also good: [stackoverflow.com: What is a virtualenv, and why should I use one?](https://stackoverflow.com/questions/41972261/what-is-a-virtualenv-and-why-should-i-use-one)

python -m venv env
    . env/bin/activate

which python
    # prints /here/env/bin/python
    which pip
    # prints /here/env/bin/pip

pip install <package>

Toggle Preview

Edit message*

A description of the changes made