unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: 30437-done@debbugs.gnu.org
Subject: bug#30437: No “.guix-profile/bin/python” after ‘guix package -i python’
Date: Mon, 12 Feb 2018 20:00:57 +0100	[thread overview]
Message-ID: <878tbykp7a.fsf@elephly.net> (raw)
In-Reply-To: <20180212182952.GB21970@macbook41>


Efraim Flashner <efraim@flashner.co.il> 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 <mthl@gnu.org> wrote:
>> 
>> > I think it would work better if when installing python@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.
>> 
>
> 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

  reply	other threads:[~2018-02-12 19:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-12 16:52 bug#30437: No “.guix-profile/bin/python” after ‘guix package -i python’ Mathieu Lirzin
2018-02-12 17:23 ` Danny Milosavljevic
2018-02-12 18:29   ` Efraim Flashner
2018-02-12 19:00     ` Ricardo Wurmus [this message]
2018-02-12 19:38   ` Mathieu Lirzin
2018-02-12 23:14     ` Ricardo Wurmus
2018-02-13  0:45       ` Mathieu Lirzin
     [not found] ` <handler.30437.D30437.151846208124209.notifdone@debbugs.gnu.org>
2018-02-12 19:55   ` bug#30437: closed (Re: bug#30437: No “.guix-profile/bin/python” after ‘guix package -i python’) Mathieu Lirzin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878tbykp7a.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=30437-done@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).