Libraries misbehaving?

I was having this problem, the system was installing libraries into python3.X and driving me nuts, as I wanted the libraries in the 2.7 branch.

Here's *a* solution, that also gave me more understanding of python/linux filestructure to change the python version system-wide (and thus where libraries are automatically installed using pip):

$update-alternatives --list python
>update-alterantives: error: no alternatives for python
$update-alternatives --install /usr/bin/python python /usr/bin/python2.7 1
$update-alternatives --install /usr/bin/python python /usr/bin/python3.4 2
$update-alternatives --list python **will now give a list of python versions that you have told it about**
$update-alternatives --config python
>type selection number to set python version system-wide

To remove a python version from this list:
$update-alternatives --remove python /usr/bin/python3.4

Once system knows which python version you wish to use as default, you can then find the default paths that python is using:
$python -c "import sys;print(sys.path)"

In addition, the pythonic shebang that you should be using at the top of scripts will now work flawlessly:
#!/usr/bin/env python

Hope this helps somebody!