/usr/bin/python* interpreters (i.e. the ones provided by Debian) use dist-packages (libraries in /usr/lib/.../dist-package - which are provided by Debian developers and /usr/local/lib/.../dist-packages - provided by system administrators)
/usr/local/bin/python* interpreters (the ones that have nothing to do with Debian, i.e. compiled by local administrators or Python upstream developers) use site-packages (/usr/local/lib/*/site-packages, and /usr/lib/.../site-packages) This way if you install files using local interpreter (/usr/local/bin/python setup.py ...), you get your local modules. Modules installed from .debs will not mess with your local interpreter and vice versa. I don't know how to explain it better. /usr/local/bin/python* and /usr/bin/python* cannot share any libraries (for various reasons, one of them is the same why /usr/bin/python2.6 and /usr/bin/python2.7 do not share any libraries either). This separation is something we had to work on, other distributions probably do not care about this that much and that's why they stick with site-packages. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
