From: Efraim Flashner <efraim@flashner.co.il>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 30437@debbugs.gnu.org, Mathieu Lirzin <mthl@gnu.org>
Subject: bug#30437: No “.guix-profile/bin/python” after ‘guix package -i python’
Date: Mon, 12 Feb 2018 20:29:52 +0200 [thread overview]
Message-ID: <20180212182952.GB21970@macbook41> (raw)
In-Reply-To: <20180212182307.7c0982ee@scratchpost.org>
[-- Attachment #1: Type: text/plain, Size: 927 bytes --]
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
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-02-12 18:31 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 [this message]
2018-02-12 19:00 ` Ricardo Wurmus
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=20180212182952.GB21970@macbook41 \
--to=efraim@flashner.co.il \
--cc=30437@debbugs.gnu.org \
--cc=dannym@scratchpost.org \
--cc=mthl@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).