On May 3, 2013, at 9:47 PM, Nick Coghlan <[email protected]> wrote: > Agreed, blessing something like Debian's solution sounds like a better idea > than changing pip's default installation location. To provide that blessing, > I think PEP 439 should be expanded to explicitly cover this aspect (there's > another subtlety, in that it may be desirable for distro packages to be > available when running with -S - I'm not sure how Debian currently handle > that). > > Essentially, my goal is to have a clearly defined, consistent, > cross-distro-and-platform shadowing behaviour for cases where you install a > Python software distribution from a system package manager *and* through pip. > The current situation, where the system tools and the Python specific tools > tread on each other's toes at the filesystem layer (unless you change the > default Python path, as Debian does) isn't appropriate for something we are > going to ship as part of the standard Python toolkit. > > (Coincidentally, this may lead to my CPython bootstrapping changes becoming > packaging related!) > > Cheers, > Nick. > This sounds excellent to me.
----------------- Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
