On 03/10/2018 13:17, Chris Angelico wrote:
On Wed, Oct 3, 2018 at 9:11 PM Dan Purgert <d...@djph.net> wrote:
Chris Angelico wrote:
On Wed, Oct 3, 2018 at 5:17 AM Thomas Jollans <t...@tjol.eu> wrote:
[...]
Whether we agree on the terminology here or not, of course we can agree
that you have to be bloody careful if you *do* decide to put things in
/usr/bin yourself :-)
[...] On my system (Debian GNU/Linux), /usr/local/bin is ahead of
/usr/bin in $PATH, so even installing into local isn't going to
protect you.
Here (MX 17), I'd also shoot myself in the foot if I installed something
as "/usr/local/bin/python" :)
$ echo $PATH
/usr/local/bin:/usr/bin
I imagine there's good reason for /usr/local/bin to override /usr/bin
... but it also seems like it's a good way to cause "fun(tm)" problems.
If a system script depends on Python, it should be calling on
/usr/bin/python2.7 explicitly, rather than depending on $PATH. (And
possibly using -E for further isolation.)
(On Red Hat systems) they tend to call /usr/bin/python.
--
https://mail.python.org/mailman/listinfo/python-list
