1. PYTHONPATH is an environment variable which you can set to add additional directories where python will look for modules and packages. e.g.:

   # make python look in the foo subdirectory of your home directory for   
   # modules and packages 
   export PYTHONPATH=${PYTHONPATH}:${HOME}/foo 
   

   Here I use the sh syntax. For other shells (e.g. csh,tcsh), the syntax would be slightly different. To make it permanent, set the variable in your shell's init file (usually ~/.bashrc).

2. Ubuntu comes with python already installed. There may be reasons for installing other (independent) python versions, but I've found that to be rarely necessary.

3. The folder where your modules live is dependent on PYTHONPATH and where the directories were set up when python was installed. For the most part, the installed stuff you shouldn't care about where it lives -- Python knows where it is and it can find the modules. Sort of like issuing the command ls -- where does ls live? /usr/bin? /bin? 99% of the time, you don't need to care -- Just use ls and be happy that it lives somewhere on your PATH so the shell can find it.

4. I'm not sure I understand the question. 3rd party modules usually come with install instructions. If you follow the instructions, python should be able to find the module and you shouldn't have to care about where it got installed.

5. Configure PYTHONPATH to include the directory where your module resides and python will be able to find your module.

The site module documentation and Modifying Python's Search Path seem to be what you're looking for.

As far as I understand it, those entries are being added to sys.path by:

• /usr/lib/python2.6/site.py
• /usr/lib/python2.6/dist-packages/site.py
  (Change 2.6 to your version of Python.)

The easiest way to change it is to add a file /usr/local/lib/python2.6/dist-packages/site-packages.pth containing ../site-packages.

Alternatively, maybe you can teach the package to use site.getsitepackages()?

I'm assuming that when you installed anaconda 2, you manually set the PYTHONPATH environment variable, by putting something like

PYTHONPATH=/home/user/anaconda2/python
export PYTHONPATH

in your .bash_profile or .bash_rc.

But since you deleted the /home/user/anacanda2/ directory, that path no longer exists.

Thus you want to change PYTHONPATH to point to the executable in /usr/lib, by changing the above to

PYTHONPATH=/usr/lib/my_python_distribution
export PYTHON

First question:

which python though its usually /usr/bin/python for the 2.7

Second question:

From a terminal & python2.7: python2.7 yourfile.py.
Simailarly for 3.2: python3.2 yourfile.py though 3.2 isn't installed by default. (You can apt-get install python3.2.)

What python yourfile.py will do depends on which alternative is used for your python interpreter. You can change that by issuing update-alternatives python as root (or by using su).

Third question:

Environment variables are shell dependent, though you can write them out with echo $variable and set them with variable=value (from bash). The search path is simply called PATH and you can get yours by typing echo $PATH.

I hope this was helpful.

As long as a custom python3 is installed in /usr/local/bin/, it will show up as the default python3 executable. why? Because by default, /usr/local/bin/ is listed earlier in the search path then /usr/bin. This way, your custom executables have priority over these installed by the system.

To make the system find /usr/bin/python3 first, you must move out /usr/local/bin/python3. The alternative would be to ticker with your PATH, moving /usr/local/bin behind, but that would affect every other custom executable.

Thus, rename /usr/local/bin/python3 to /usr/local/bin/python3cust or something. Then, you will be using the default python version.

On Ubuntu, you actually may not change the default python version. Python is extensively used in the operating system. Changing the version will likely break things.

Since you have Linux, and if you want to simply type "python" instead of "python3" in order to run Python programs, a solution is simply to define an alias in you shell configuration file (.bashrc, etc.). For Bourne shells, it should be something like

alias python=python3

(or whatever your Python 3 name is).

This way, you do not have to change anything on your system, so this solution should quite innocuous and it should not break your system.

It's not good to change the default python. Many system programs depends on python2 not python3. if you want to use python3, you just type the command python3.