From: Leo Famulari <leo@famulari.name>
To: zimoun <zimon.toutoune@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Python 2 and Python 3 ?
Date: Fri, 23 Feb 2018 12:36:55 -0500 [thread overview]
Message-ID: <20180223173655.GB24390@jasmine.lan> (raw)
In-Reply-To: <CAJ3okZ2PBhXf+_JSxrXNh+Nzw0bCThtqfptH1kasiESepr6-6w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1212 bytes --]
On Fri, Feb 23, 2018 at 06:27:30PM +0100, zimoun wrote:
> I am asking if this behaviour is expected or if I miss something.
>
> The command:
>
> guix package -i python
>
> installs the python3 version and there is no python in .guix-profile/bin/.
>
> And in another profile `guix package -i python@2' installs the python2
> and there is python in profile/bin/.
>
>
> To me, it is counter-intuitive. What is the reason ?
> And there is not any, since python 2 is dying, I suggest that python
> points to python3 and not python2.
The recommendation by the CPython team, expressed in their build
scripts, is to install Python 3 as `python3`, and we try to follow
upstream as closely as we can. I'd guess their reason is long-term
compatibility with existing Python software that assumes `python` is
Python 2.
We offer Python 3 as `python` in the special package python-wrapper.
In general, Guix does default to Python 3. If you want to use Python 2
in a package or profile, you have to specify it. Otherwise, using the
package named 'python' will give you Python 3. If there are several
versions of a Guix package with the same name, Guix uses the latest
version by default.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-02-23 17:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-23 17:27 Python 2 and Python 3 ? zimoun
2018-02-23 17:36 ` Leo Famulari [this message]
2018-02-23 18:26 ` zimoun
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=20180223173655.GB24390@jasmine.lan \
--to=leo@famulari.name \
--cc=help-guix@gnu.org \
--cc=zimon.toutoune@gmail.com \
/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.
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).