You can use the Site-specific configuration hook.

"A path configuration file is a file whose name has the form name.pth and exists in one of the four directories mentioned above; its contents are additional items (one per line) to be added to sys.path."

In your case, you should be able to achieve what you want by simply dropping in a .pth file containing the path of the directory to include:

[root@home]$ echo "/usr/local/lib/python2.7/site-packages/" > /opt/python2.7.2/lib/python2.7/site-packages/usrlocal.pth

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()?

(Please correct errors and omissions as necessary. Thanks.)

First, a question and a comment. I don't use SUSE, so take this with a pinch of salt. Are the packages that install in /usr/lib/python2.6/site-packages official packages? If so, SUSE is broken, so that is not likely. If they are not official packages, you could either ask the packagers to use the standard paths, or, alternatively, you could submit a wishlist bug to SUSE asking them to support this additional path. This will save you and other people additional headaches.

For the moment, you have the following possibilities, in order of decreasing scope:

1. Change the module search path for all users (method 1)

   Change the module search path in the Python installation.

   The default module search path is hardwired into the binary. Add-on paths can be configured at runtime, for example in the site.py file. For example, Debian uses /usr/lib/python2.6/site.py (for the default python 2.6 installation) to do its site-specific configuration. At the top of the file is written

   Append module search paths for third-party packages to `sys.path`.
   
   ****************************************************************
   * This module is automatically imported during initialization. *
   ****************************************************************
   [...]
   
   This will append site-specific paths to the module search path.
   

   The Debian patch debian/patches/site-locations.diff says

   For Debian and derivatives, this sys.path is augmented with directories for packages distributed within the distribution. Local addons go into /usr/local/lib/python/dist-packages, Debian addons install into /usr/{lib,share}/python/dist-packages. /usr/lib/python/site-packages is not used.

   The patch in question is

                   sitedirs.append(os.path.join(prefix,
   "Lib", "site-packages"))
                elif os.sep == '/':
       +            sitedirs.append(os.path.join(prefix,
   "local/lib",
       +                                        "python" + sys.version[:3],
       +                                        "dist-packages"))
                    sitedirs.append(os.path.join(prefix,
   "lib",
                                                "python" + sys.version[:3],
       -                                        "site-packages"))
       -            sitedirs.append(os.path.join(prefix,
   "lib", "site-python"))
       +                                        "dist-packages"))
       +            sitedirs.append(os.path.join(prefix,
   "lib", "dist-python"))
                else:
                    sitedirs.append(prefix)
                    sitedirs.append(os.path.join(prefix,
   "lib", "site-packages"))
   

   So you could modify the site.path in your system package to produce a modified module search path. You probably don't want to this, though. For one thing, you will have to merge this in on every update of your distribution's python package.

2. Change the module search path for all users (method 2)

   Add a file of the form something.pth to a directory that is already in the search path, which contains a path, either relative or absolute. Eg.

   /usr/local/lib/python2.6/dist-packages$ cat foo.pth 
   /home/faheem/dummypythonpath
   

   In another terminal do

   >>> import sys
   >>> sys.path
       [...,'/home/faheem/dummypythonpath',...,]
   

3. Change the module search path for all users (method 3)

   The environment variable PYTHONPATH is normally used to append to the system path at user level. You can put it in a file which will be sourced by all users. Eg. in Debian we have /etc/bash.bashrc, which says at the top

   # System-wide .bashrc file for interactive bash(1) shells.
   
   # To enable the settings / commands in this file for login shells as well,
   # this file has to be sourced in /etc/profile.
   

   So you could add or PYTHONPATH there. You probably want it to be sourced for both login and interactive shells, so you'll want to check on that. Unfortunately, distributions are often flaky about enabling this.

   The paths in PYTHONPATH are added to the default list of search paths in the system (which can be obtained for example by sys.path - see below). Allowing for the possibility that PYTHONPATH is set already, just add desired additional directories to it, eg.

   export PYTHONPATH=$PYTHONPATH:"/home/username/lib/python2.6/dist-packages"
   

   If you source the PYTHONPATH variable, and then check sys.path again, you will
   see the paths have been added. Note that the position in which the paths in
   PYTHONPATH are added to the pre-existing paths does not seem to be prescribed by
   the implementation.

4. Change the module search path per user.

   The usual way is to change PYTHONPATH in the user's bashrc, namely ~/.bashrc. Again, check that it is sourced for both login and interactive shells.

5. Change the module search path on a per script basis. This is done by appending to sys.path, namely

   import sys
   sys.path.append(some_additional_path)
   

   This will only work for the script that is importing this. This is normally used, as far as I know, for casual use, when importing modules in nonstandard locations, like from somewhere in a home directory.

See also Greg Ward on Modifying Python's Search Path. This has a good discussion of the available alternatives.

Try $PYTHONPATH instead of $PATH in your bash configuration file. For more info look at the official documentation on this topic.

If you're using bash (on a Mac or GNU/Linux distro), add this to your ~/.bashrc

export PYTHONPATH="${PYTHONPATH}:/my/other/path"

just put the folder in site-packages directory. ie:

C:\PythonXY\Lib\site-packages

Note: you need to add an empty file __init__.py to the folder

Files named __init__.py are used to mark directories on disk as a Python package directories.

If you have the files:

C:\PythonXY\Lib\site-packages\<my_library_folder>\__init__.py
C:\PythonXY\Lib\site-packages\<my_library_folder>\module.py

you can import the code in module.py as:

from <my_library_folder> import module

If you remove the __init__.py file, Python will no longer look for submodules inside that directory, so attempts to import the module will fail.

If you have lots of folders, then create the empty __init__.py file in each folder. for eg:

C:\PythonXY\Lib\site-packages\<my_library_folder>\
    __init__.py
    module.py        
    subpackage\
        __init__.py
        submodule1.py
        submodule2.py

Add /Library/Python/2.6/site-packages to your PYTHONPATH.

(Spyder maintainer here) We forbid adding site-packages directories through our PYTHONPATH manager because it allows people to mix two different Python versions (which is what you're trying to do by adding your system site-packages to your Anaconda's Python).

And we do that because it usually generates odd errors and segfaults for binary packages such as Numpy, Pandas and Matplotlib, given that binary packages for one Python version are incompatible with packages for another one.

Finally, even though you found a workaround for that (by using sys.path), we strongly suggest you to stop doing that because it'll give you nothing by headaches in the future.