From: Alex Kost <alezost@gmail.com>
To: Ian Denhardt <ian@zenhack.net>
Cc: guix-devel@gnu.org
Subject: Re: Problems with downloading from https
Date: Thu, 30 Oct 2014 22:08:08 +0300 [thread overview]
Message-ID: <87ioj1e5pj.fsf@gmail.com> (raw)
In-Reply-To: <20141030170541.1141.14634@rook.local.tld> (Ian Denhardt's message of "Thu, 30 Oct 2014 13:05:41 -0400")
Ian Denhardt (2014-10-30 20:05 +0300) wrote:
> Quoting Alex Kost (2014-10-30 03:27:59)
>> As both python packages can co-exist in one profile, either python-2…
>> may be renamed into “python2” or python-3… into “python3”. As python3
>> is the future, I think it would be better to have “python2” and “python”
>> (which is python3) packages. Or maybe they shouldn't be renamed and we
>> can introduce a little collision instead by adding "…/bin/python"
>> symlink to python-3… package.
>
> Speaking as someone who's been on a distro that has python 3 as the
> default since 2.7 came out, and being a professional python developer
> working on codebases that often don't work on python 3, I don't really
> consider this a sensible default. I often have a symlink ahead of the
> system python binary in my path that points to python2. More
> importantly, I think it should be tunable. I *do* sometimes make use of
> having both available.
This is what you currently have: you can install both, and "python" would
be a link to "python2".
But installing 2 packages with the same name is not intended (to prevent
file names collision), so I think it would be better to rename one of the
pythons into "python2"/"python3".
--
Alex
next prev parent reply other threads:[~2014-10-31 15:31 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-25 17:30 Problems with downloading from https Alex Kost
2014-10-25 20:02 ` Ian Denhardt
2014-10-26 7:03 ` Alex Kost
2014-10-26 13:46 ` Ludovic Courtès
2014-10-26 19:35 ` Alex Kost
2014-10-26 21:01 ` Ludovic Courtès
2014-10-27 9:06 ` Mark H Weaver
2014-10-27 12:24 ` Ludovic Courtès
2014-10-27 12:44 ` Ludovic Courtès
2014-10-27 13:27 ` Alex Kost
2014-10-27 14:43 ` Mark H Weaver
2014-10-27 16:24 ` Ludovic Courtès
2014-10-27 16:44 ` Alex Kost
2014-10-28 8:03 ` Ludovic Courtès
2014-10-29 22:22 ` Andreas Enge
2014-10-30 7:27 ` Alex Kost
2014-10-30 7:49 ` Andreas Enge
2014-10-30 12:31 ` Alex Kost
2014-10-30 12:38 ` Andreas Enge
2014-10-30 19:30 ` Alex Kost
2014-10-30 23:07 ` Different versions of a package in the same profile? Ludovic Courtès
2014-11-01 10:46 ` Andreas Enge
2014-11-02 17:22 ` Ludovic Courtès
2014-11-02 17:39 ` Andreas Enge
2014-10-30 13:20 ` Problems with downloading from https Ludovic Courtès
2014-10-30 17:05 ` Ian Denhardt
2014-10-30 19:08 ` Alex Kost [this message]
2014-10-31 4:54 ` Ian Denhardt
2014-10-30 14:48 ` Ludovic Courtès
2014-10-27 13:01 ` Alex Kost
2014-10-27 14:32 ` Mark H Weaver
2014-10-25 21:53 ` Ludovic Courtès
2014-10-26 5:30 ` [PATCH 0/1] " Ian Denhardt
2014-10-26 5:21 ` [PATCH 1/1] README: add a note about optional GnuTLS dependency Ian Denhardt
2014-10-27 12:54 ` Ludovic Courtès
2014-10-27 10:49 ` [PATCH 0/1] Re: Problems with downloading from https Ian Denhardt
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=87ioj1e5pj.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ian@zenhack.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.