On May 3, 2013, at 6:29 AM, Nick Coghlan <ncogh...@gmail.com> wrote: > Because sysadmins don't participate in upstream development and non-platform > provided tools messing with /usr is wrong, wrong, wrong. > > The system Python is the domain of distro tools, we should be leaving it the > hell alone. > > Cheers, > Nick. >
To be honest your proposal doesn't really do that since you want it to install
into the site-packages if they are running it as root. If that's you're
argument you should at least be consistent within your own proposal. One of my
main problems with your proposal is that we suddenly have surprising behavior
about where packages are being installed to:
Linux + root user = site-packages
Linux + regular user = user-packages (<-- Going to confuse people because
it's different)
Linux + regular user + virtualenv = site-packages
I don't know much about RHEL, but Debian "installing globally" means installing
into /usr/local/lib/pythonX.Y/site-packages/ which is exactly where Debian
wants you to put python libraries not installed via apt. Apt drops things
into /usr/local/lib/pythonX.Y/dist-packages.
Even if installing into the "system" python globally is wrong is there even a
way too determine if we are attempting to install into a *system* python or
not? I could be wrong but afaik there's not a good way to determine if this is
a python that is managed by the system or one that was installed otherwise. If
that's the case then we break by default one of the viable methods of isolation
*from* system. This is very popular on OSX where people tend to install a non
system python via homebrew to isolate themselves.
-----------------
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 - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
