At 11:33 PM 2/19/2006 -0800, Jeff Pitman wrote: >On 2/8/06, Phillip J. Eby <[EMAIL PROTECTED]> wrote: > > I'm really curious how this particular Python got built, such that it > > thinks /usr/lib64 is the place where this stuff goes. > >I think Fedora on AMD 64 has special issues with things going into >/usr/lib64 vs. /usr/lib. I don't have one myself, I can only speak >from messages that have been posted and also recommended packaging >"policies" for the AMD 64 platform. > >32-bit is normally: > > >>> from distutils.sysconfig import get_python_lib; print get_python_lib() >/usr/lib/python2.4/site-packages > >>> from distutils.sysconfig import get_python_lib; print get_python_lib(1) >/usr/lib/python2.4/site-packages > >64-bit turns out to be something like this (cannot guarantee, but similar): > > >>> from distutils.sysconfig import get_python_lib; print get_python_lib() >/usr/lib/python2.4/site-packages > >>> from distutils.sysconfig import get_python_lib; print get_python_lib(1) >/usr/lib64/python2.4/site-packages
Luckily, setuptools 0.6a10 uses not only the results from get_python_lib() to scope out site-packages directories, but if the directory isn't on PYTHONPATH and isn't otherwise known, it will actually spawn a process to test whether .pth files work in that directory. If they do, installation proceeds with no further questions asked. _______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
