From: ludo@gnu.org (Ludovic Courtès)
To: Konrad Hinsen <konrad.hinsen@fastmail.net>
Cc: guix-devel@gnu.org
Subject: Re: installing python 2 and python 3 in the same profile
Date: Thu, 15 Mar 2018 10:11:48 +0100 [thread overview]
Message-ID: <874llhwvmz.fsf@gnu.org> (raw)
In-Reply-To: <38c1da8e-5af7-7e6d-f754-8dcf4a13c0b7@fastmail.net> (Konrad Hinsen's message of "Wed, 14 Mar 2018 15:30:08 +0100")
Hi,
Konrad Hinsen <konrad.hinsen@fastmail.net> skribis:
> On 14/03/2018 12:39, Hartmut Goebel wrote:
>> Am 13.03.2018 um 22:52 schrieb Ludovic Courtès:
>>> 2. Use different package names when we know things can be
>>> parallel-installed: “python2” vs. “python” (I’m talking about the
>>> package name, not its version string.) That’s what distros usually
>>> do, and I think it’s good enough.
>>
>> I'd prefer this.
>
> That sounds like a good basis. But perhaps "python" for Python 2 and
> "python3" for Python 3 would make more sense, since those are the
> names of the executables.
Yes. OTOH we use the “python2-” prefix for 2.x packages and “python-”
for 3.x packages.
At any rate, that’s a change we should do now in ‘core-updates’.
Ricardo?
> This does of course raise the question of how this will evolve in the
> long run, but since so many bad decisions were already taken, I am not
> trying to guess what will happen. For now, the upstream recommendation
> remains to use "python" and "python3" to distinguish the
> executables. But what will happen in 2020? The Python community might
> be tempted to change the naming to mark the end of Python 2 support,
> but that would be at the price of another round of breaking
> everybody's scripts.
Not our business I’d say. :-)
Ludo’.
next prev parent reply other threads:[~2018-03-15 9:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 7:50 installing python 2 and python 3 in the same profile Ricardo Wurmus
2018-03-10 8:34 ` Pjotr Prins
2018-03-11 9:11 ` Konrad Hinsen
2018-03-11 11:10 ` Ricardo Wurmus
2018-03-11 12:42 ` Pjotr Prins
2018-03-11 13:30 ` Hartmut Goebel
2018-03-11 13:36 ` Pjotr Prins
2018-03-12 7:07 ` Konrad Hinsen
2018-03-12 8:37 ` Ricardo Wurmus
2018-03-11 13:00 ` Hartmut Goebel
2018-03-11 13:27 ` Pjotr Prins
2018-03-13 21:52 ` Ludovic Courtès
2018-03-14 8:40 ` Ricardo Wurmus
2018-03-14 11:39 ` Hartmut Goebel
2018-03-14 14:30 ` Konrad Hinsen
2018-03-15 9:11 ` Ludovic Courtès [this message]
2018-03-15 9:37 ` Konrad Hinsen
2018-03-16 20:59 ` Ricardo Wurmus
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874llhwvmz.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=konrad.hinsen@fastmail.net \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.