emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#30437: closed (No “.guix-profile/bin/python” after


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#30437: closed (No “.guix-profile/bin/python” after ‘guix package -i =?UTF-8?Q?python=E2=80=99?=)
Date: Mon, 12 Feb 2018 19:02:02 +0000

Your message dated Mon, 12 Feb 2018 20:00:57 +0100
with message-id <address@hidden>
and subject line Re: bug#30437: No “.guix-profile/bin/python” after ‘guix 
package -i python’
has caused the debbugs.gnu.org bug report #30437,
regarding No “.guix-profile/bin/python” after ‘guix package -i python’
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
30437: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=30437
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: No “.guix-profile/bin/python” after ‘guix package -i python’ Date: Mon, 12 Feb 2018 17:52:41 +0100 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux)
Hello,

I think it would work better if when installing address@hidden, 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.

Thanks for considering it.

-- 
Mathieu Lirzin
GPG: F2A3 8D7E EB2B 6640 5761  070D 0ADE E100 9460 4D37



--- End Message ---
--- Begin Message --- Subject: Re: bug#30437: No “.guix-profile/bin/python” after ‘guix package -i python’ Date: Mon, 12 Feb 2018 20:00:57 +0100 User-agent: mu4e 0.9.18; emacs 25.3.1
Efraim Flashner <address@hidden> writes:

> On Mon, Feb 12, 2018 at 06:23:07PM +0100, Danny Milosavljevic wrote:
>> Hi Mathieu,
>> 
>> On Mon, 12 Feb 2018 17:52:41 +0100
>> Mathieu Lirzin <address@hidden> wrote:
>> 
>> > I think it would work better if when installing address@hidden, 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.
>> 
>
> We do also have the 'python-wrapper' package which uses python3 as
> python

Closing because it’s not a bug.

-- 
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net




--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]