@FaheemMitha for what it's worth apt and pip often/usually use different trees
stackoverflow.com/questions/9387928/… . Furthermore, it's considered a good practice to use virtualenvs for your own (non-system) stuff so that you don't step on the toes of the system python. In that case everything is in the virtualenv's local tree. Or at least you can use
pip install --user
which would put it in
~/.local/lib/python*/site-packages