python library path on Debian LInux

Paul Wright -$Paul$- at verence.demon.co.uk
Wed Oct 17 09:09:43 EDT 2001


In article <mailman.1003274776.22998.python-list at python.org>,
Avdi B. Grimm <avdi at avdi.org> wrote:
>I'm using Python on a Debian machine, and I've installed both the
>python-1.5 and the python2 packages.  I prefer to use python2.
>Unfortunately, the way the Debian packages are arranged, many of the
>additional libraries available for python (such as PyGTK) are as yet
>only packaged for Python1.5. Apparently libraries packaged for different
>Python versions are installed in different directories, and each python
>executable only sees the libs that were packaged for it.

Yes. What I do is get binaries from stable and source from testing: 

deb ftp://ftp.uk.debian.org/debian/ stable main non-free contrib
deb-src ftp://ftp.uk.debian.org/debian/ testing main non-free contrib
deb http://non-us.debian.org/debian-non-US stable/non-US main contrib non-free
deb-src http://non-us.debian.org/debian-non-US testing/non-US main contrib non-free

deb http://security.debian.org/ stable/updates main contrib non-free

When I want something which isn't in stable, or a more recent version of
something which is, I get the source from testing and build the package.

I'm doing it this way because I don't know how reliable the testing
distribution is at the moment so I'm not quite willing to make the jump
to it yet, but if you need the latest stuff and have a fast connection,
upgrading to testing is probably the easiest way to do it.

-- 
----- Paul Wright ------| /dev/hda - 3.2Gb of spinning metal, all alone in
-paul.wright at pobox.com--| the night...
http://pobox.com/~pw201 | 



More information about the Python-list mailing list