https://bugzilla.novell.com/show_bug.cgi?id=637176 https://bugzilla.novell.com/show_bug.cgi?id=637176#c2 Matt Williams <matt@milliams.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|matt@milliams.com | --- Comment #2 from Matt Williams <matt@milliams.com> 2010-09-06 21:44:57 UTC --- (In reply to comment #1)
this should be easy to add - but the .local hierarchy is poorly specified. do you have any references about "lib64" even being present in ".local" ?
While there are no documented references to lib64 (that I can find in the PEP or in docs.python.org), there are packages that install themselves there. For example, PyYaml (http://pypi.python.org/pypi/PyYAML), installs itself to lib64. This package doesn't mention 'lib64' anywhere in its source code but it uses distutils to install. This suggests that distutils is set to automatically install to lib4 on 64 bit systems. AFAICT, distutils uses the get_python_lib() (http://docs.python.org/distutils/apiref.html?highlight=sysconfig#distutils.s...) function to get the install path for compiled code. Running: % python -c "from distutils import sysconfig;print(sysconfig.get_python_lib(True, prefix='~/.local'))" ~/.local/lib64/python2.6/site-packages is the the path that compiled code will be installed to. I'm guessing that at some point in its compilation Python is told that on x86_64 systems, libs should be installed into 'lib64'. Either that or Python is guessing this itself. I know that the same happen with code not installed into ~/.local -- If you pass no 'prefix' to get_python_lib() the it gives '/usr/lib64/python2.6/site-packages'. There is some discussion of this at http://serverfault.com/questions/60619/fedora-usr-lib-vs-usr-lib64. Cheers, Matt -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.