On Jul 5, 11:09 am, david <[EMAIL PROTECTED]> wrote: > You learn something new every day: > > On my ubuntu, update-manager is supposed to use the python2.5 > installed on /usr/bin. Well, I had subsequently installed a whole > bunch of stuff in /usr/local (/usr/local/bin/python and /usr/local/lib/ > python2.5 etc), which I have happily been using for development for a > year. I had thought that the two pythons were completely independent. > > Well, I was wrong. When /usr/bin/python2.5 runs, *by default*, it > adds /usr/local/lib/python2.5 to its sys path - and apparently there > are things in /usr/local which are inconsistent with those at /usr > (not suprising). > > I have fixed the problem - but I had to modify the actual update- > manager .py file itself. At the beginning, I set the sys.path in > python *explicitly* to not include the /usr/local stuff. > > But this is clearly a kludge. My question: how do I keep the Ubuntu > python stuff at /usr/bin/python2.5 from adding /usr/local/lib/ > python2.5 to the import search path in a clean and global way? I > really want both pythons completely isolated from one another! > > Thankyou.
When you install a second version, let us say Python3.0, you want to download the source and do the normal config and make but not make install. Instead do a make altinstall. They will be kept separate. I have Ubuntu's 2.5 as well as 3.0. Ubuntu installs to /usr/bin and / usr/lib, so I installed 3.0 from /usr/local/Python-3.0 and those files installed into /usr/local/bin and lib and the executable is python3.0. Take a look at the README file that comes with the source code for other options. -- http://mail.python.org/mailman/listinfo/python-list
