From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: guix-devel@gnu.org
Subject: Re: installing python 2 and python 3 in the same profile
Date: Sun, 11 Mar 2018 10:11:18 +0100 [thread overview]
Message-ID: <af5ae80d-46c4-027f-cfb1-d846d79d5816@fastmail.net> (raw)
In-Reply-To: <20180310083421.GA26219@thebird.nl>
On 10/03/2018 09:34, Pjotr Prins wrote:
>> It still works with ad-hoc environments, but manifests containing both
>> Python versions cannot be instantiated any more. This is too strict,
>> because we know that these two variants don’t cause conflicts.
>
> That is not my experience. Any mix is a problem.
I agree. Even if "it works" superficially, it's hard to do serious work
with Python when you have the two versions in the same profile.
In fact, I find that Guix is the best package manager for dealing with
this precisely because it allows me to have multiple independent profiles.
> I suggest not to go there. Teach people about profiles and
> environments and all should be fine. You can support Python 3, Python
Yes, and perhaps make working with profiles a bit easier. For example,
I'd appreciate a "guix profile" resembling "guix environment":
guix profile ~/profiles/python2
would start a shell with the python2 profile, and
guix profile ~/profiles/python2 command
would run "command" in the context of the profile. This is actually on
my to-do list.
> I must add that in most of my Guix experience I relied on
> $HOME/.guix-profile. But these days I hardly use that anymore. Just
> for some basic desktop tooling. Using multiple profiles is the only
> way to mix versions and keep a level of sanity.
Same here.
Konrad.
next prev parent reply other threads:[~2018-03-11 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 [this message]
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
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
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=af5ae80d-46c4-027f-cfb1-d846d79d5816@fastmail.net \
--to=konrad.hinsen@fastmail.net \
--cc=guix-devel@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).