From: ludo@gnu.org (Ludovic Courtès)
To: Cyril Roelandt <tipecaml@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Python 3 binaries
Date: Sat, 31 Aug 2013 20:20:44 +0200 [thread overview]
Message-ID: <87wqn1rabn.fsf@gnu.org> (raw)
In-Reply-To: <5222282D.7000801@gmail.com> (Cyril Roelandt's message of "Sat, 31 Aug 2013 19:30:21 +0200")
Cyril Roelandt <tipecaml@gmail.com> skribis:
> On 08/31/2013 05:30 PM, Andreas Enge wrote:
>> Hello,
>>
>> python 3 does not ship a python binary any more, just a binary called
>> python3. That could be useful, since it would allow to install python 2 and 3
>> side by side. However, all packages relying on a shebang substitution with
>> a python binary now fail.
>>
>> I see two general possibilities to solve the problem:
>> - The simplest one, add a symlink python->python3 in the python 3 package.
>> But then we lose the possibility of installing python 2 and 3 at the same
>> time. Which maybe does not matter? It would only be a problem for a user
>> wanting to install both in the user profile, while all other packages
>> would internally have rewritten their calls to either of the two python
>> versions
>
> I think lots of users would want that. On Debian, I really like having
> multiple versions of Python, since some of my scripts are not Python3
> compatible. It's also useful to run test suites against many versions
> of Python. I think users must be able to install both.
Yes, and that’s visibly what upstream wants. So I would just leave
things as is, without the symlink.
Then again I know nothing about Python. :-)
Ludo’.
next prev parent reply other threads:[~2013-08-31 18:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-31 15:30 Python 3 binaries Andreas Enge
2013-08-31 17:30 ` Cyril Roelandt
2013-08-31 18:20 ` Ludovic Courtès [this message]
2013-09-01 9:28 ` Andreas Enge
2013-09-01 10:03 ` Andreas Enge
2013-09-01 14:03 ` Ludovic Courtès
2013-09-01 14:39 ` Andreas Enge
2013-09-01 17:34 ` Ludovic Courtès
2013-09-01 17:40 ` Cyril Roelandt
2013-09-01 18:21 ` Andreas Enge
2013-09-01 17:50 ` Andreas Enge
2013-09-02 6:24 ` Brandon Invergo
2013-09-08 18:35 ` Andreas Enge
-- strict thread matches above, loose matches on Subject: below --
2013-09-01 8:20 Brandon Invergo
2013-09-01 13:49 ` Andreas Enge
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=87wqn1rabn.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=tipecaml@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.
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).