On Sep 13, 2010, at 05:04 PM, Antoine Pitrou wrote: >On Mon, 13 Sep 2010 10:55:16 -0400 >Barry Warsaw <barry at python.org> wrote: >> On Sep 13, 2010, at 04:36 PM, Antoine Pitrou wrote: >> >> - /usr/share/pyshared/foo.cpython-32m.so >> >> - /usr/share/pyshared/foo.cpython-33m.so >> >> + /usr/lib/python/foo.cpython-32m.so >> >> + /usr/lib/python/foo.cpython-33m.so >> > >> >Are these the default paths? The PEP doesn't say how a distribution >> >is supposed to choose its PEP 3149 filesystem layout (instead of >> >/usr/lib/python3.2/site-packages). >> >> Why should it? Distributions are going to make their own decisions >> independent of the PEP. That's why s/would/might/ in the above >> change. I'm open to suggestions for better ways to explain it. > >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). -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: <http://mail.python.org/pipermail/python-dev/attachments/20100913/6600aa37/attachment.pgp>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4