GNU bug report logs -
#30437
No “.guix-profile/bin/python” after ‘guix package -i python’
Previous Next
Reported by: Mathieu Lirzin <mthl <at> gnu.org>
Date: Mon, 12 Feb 2018 16:53:01 UTC
Severity: normal
Done: Ricardo Wurmus <rekado <at> elephly.net>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
Hi,
Danny Milosavljevic <dannym <at> scratchpost.org> writes:
> On Mon, 12 Feb 2018 17:52:41 +0100
> Mathieu Lirzin <mthl <at> gnu.org> wrote:
>
>> I think it would work better if when installing python <at> 3, a ‘python’
>> executable would be available in the PATH. Maybe there is a technical
>> reason for not doing so, but I find its absence rather confusing.
>
> For backward compatibility, the 'python' executable always has to be Python 2.
>
> A lot of old scripts specify just "/usr/bin/env python" in the shebang.
>
> On the other hand if your script supports Python 3 you know it.
Hum, then I don't understand why we aren't applying this argument to
every interperter (Perl, Guile, ...) which introduce backward
incompatible changes?
--
Mathieu Lirzin
GPG: F2A3 8D7E EB2B 6640 5761 070D 0ADE E100 9460 4D37
This bug report was last modified 7 years and 102 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.