On 26 April 2017 at 19:19, Michal Cyprian <mcypr...@redhat.com> wrote: > The other possibility is to limit the pip install location change > to distutils and pip [2]. This is the "safer" option, but does > not cover all corner cases. For example, Python software built > locally using cmake or similar tools will be installed into > /usr/lib and can conflict with system tools. Debian chose to > implement similar solution.
Re-reading https://fedoraproject.org/wiki/Changes/Making_sudo_pip_safe after the discussion on the main devel list, I have a few further comments on this point: 1. I think the tone of the change proposal should be softened to say it's about make "sudo pip install" *safer*, rather than about making it absolutely safe - you can still break your system if you're not careful, the layout change just makes it easier to recover if you do (at least in most cases) 2. The question of installation directories other than site-packages (mostly notably /usr/bin) should be explicitly covered, and either also moved under /usr/local, or else a rationale given for not moving them yet 3. The proposal should be more explicitly scoped by specifying some sequences of operations that you want to make safe, such as: $ sudo pip3 install contextlib2 && sudo pip3 uninstall contextlib2 $ sudo pipsi install ansible && sudo pipsi uninstall ansible (Getting the latter example to be safe would require changing the install directory to /usr/local in a way that "pipsi" detects) Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
