On Thu, Mar 22, 2012 at 10:38:56PM -0500, [email protected] wrote: > In trying to build the subject package I ran into a problem. > However, there's was a happy ending so I've been left with > just a couple of (philosophical?) questions. > [...] > > Luckily, I caught on to what was going on relatively fast and > made 'make' finally behave by setting > PYTHONPATH=/usr/lib/python2.6/site-packages > > Whence, two questions > > 1. One strange: why 'make' wouldn't work with just > PYTHONPATH=/usr/lib/python2.6 ? > > 2. Where did I miss the existence and then the setting of a > "PYTHONPATH" ? > I do have a "PYTHONDOCS=/usr/share/doc/Python-2.7.2" from > the "Python-2.7.2" installation, but evidently I missed the > text on and importance of PYTHONPATH somewhere. > > Any comments will be warmly appreciated. > -- Alex You have Python-2.6 and 2.7 ? If so, perhaps you didn't reinstall *all* the packages which create python modules ?
I have to admit that upgrading Python2 on an existing system is something I still don't understand how to do. So far, I've taken the view that the risks, for me, of the vulnerabilities outweigh the potential risks of trashing everything in a botched upgrade ;) ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
