[Python-Dev] PEP: per user site-packages directory (original) (raw)

Barry Warsaw barry at python.org
Mon Jan 14 21:07:20 CET 2008

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On Jan 14, 2008, at 2:13 PM, glyph at divmod.com wrote:

~/bin comes from the convention of "./configure --prefix=$HOME", as autoconf suggests. This means users must have visible directories in their home folder named (among other things) "bin", "share", "lib", "src", "sbin", "man", and "include". I find this ugly. I only find it slightly less ugly that Python will now hide its locally-installed library files from me but not its locally-installed executable scripts.

"./configure --prefix=$HOME/.local" will instead put things into ~/.local/bin, ~/.local/lib, etc. Now, I am aware that setup.py already has a special "--home" option, and it can be incompatibly changed, but I don't see a reason for this. Note that --home $HOME will currently put files into ~/lib, not ~/.local/ lib. (and --home $HOME/local will put scripts into ~/.local/bin, not ~/ bin). But, now that I've told you what I think in more detail, unless you like my ideas and have specific questions, I will try to refrain from commenting further, lest I dig my own bike shed here :).

I feel pretty strongly that ~/bin should not be used. It makes
sense to me that ~/.local would mirror /usr/local.

-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin)

iQCVAwUBR4vA+XEjvBPtnXfVAQICEgP8CAuFVzZld1769uQKDWj2h4Y7x+besq5o 9bujNYJ6SayNac4u1jWLWmCIdBSuQU6/xNF6+ljpn5Pz4H/yRBl/HK2ibF2ksZwg quv23PHLvMnLju77FNKE5VclVJk3rBKpkpjmS/yXMcyfBwAccIDEJY+QUshtQzql 8mRZ4cEUP0I= =gepD -----END PGP SIGNATURE-----

More information about the Python-Dev mailing list