RetroSearch Browse

Mon Sep 13 17:04:52 CEST 2010 · http://mail.python.org/pipermail/python-dev/2010-September/103608.html

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:
> 
> >On Mon, 13 Sep 2010 16:18:44 +0200 (CEST)
> >barry.warsaw <python-checkins at python.org> wrote:
> >>  
> >> -For an arbitrary package `foo`, you would see these files when the
> >> +For an arbitrary package `foo`, you might see these files when the
> >>  distribution package was installed::
> >>  
> >> -    /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?

Thanks

Antoine.

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://mail.python.org/pipermail/python-dev/2010-September/103608.html below:

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