[Python-Dev] r84775 - peps/trunk/pep-3149.txt

["Martin v. Löwis"]

Am 13.09.2010 17:36, schrieb Antoine Pitrou:
> 
>>> I meant how these decisions are implemented. Is there a configure
>>> switch (there doesn't seem to be)? Does it require patching Python?
>>
>> Ah, no.  Standard configure switches are used.  Debian (inherited by Ubuntu)
>> has a post-installation script for Python packages which create the .py
>> symlinks and do the byte-compilation.  The big win here is that much of this
>> can go away now (and in fact there are modifications to this post-installation
>> script already).
> 
> Ok, so can you explain how the new thing will work (on Debian)? :)
> Does it mean that e.g. /usr/lib/python3.2/site-packages will get
> symlinked to /usr/lib/python?

They currently get /usr/lib/pyshared/<version> onto sys.path, by
providing a .pth file (python-support.pth). There are many other ways:
you can edit site.py, provide a sitecustomize.py, or edit Modules/Setup
(providing a Modules/Setup.local may also work).

If I was them, I wouldn't relocate the standard extension modules, but
keep them in lib-dynload; /usr/lib/pyshared would only be there for
additional packages (which then don't need to bring /usr/lib/python3.3
into existance even though python 3.3 isn't installed).

Regards,
Martin