From: Andreas Enge <andreas@enge.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Python 3 binaries
Date: Sun, 1 Sep 2013 16:39:07 +0200 [thread overview]
Message-ID: <20130901143907.GA23394@debian> (raw)
In-Reply-To: <87d2osoczg.fsf@gnu.org>
On Sun, Sep 01, 2013 at 04:03:47PM +0200, Ludovic Courtès wrote:
> Ah, so packages that work with Python 3 expect a ‘python’ (and not
> ‘python3’) executable?
Apparently so. And anyway, packages that work with both versions usually
start their scripts with #!/usr/bin/python.
> Then that’s a different story (I thought ‘python3’ was the official name
> for the binary.)
>
> I’d rather not have specific things like that in ‘patch-shebangs’. So,
> what we could do is:
> • Leave ‘python-3’ as is, without the symlink.
> • Add a ‘python-3-wrapper’ package that just contains ‘bin/python’
> pointing to ‘…/bin/python3’ (using ‘trivial-build-system’.)
> • When building Python 3 packages, we’d use the wrapper, not the real
> one; however, users would install the real one in their environment.
This would be a possibility.
Personally, I find the solution rewriting the shebangs cleaner, but this
is more a matter of taste than anything.
The wrapper would require the user to install both python-3 and the wrapper
(or contain python-3 as a propagated input), so that the user has all files
in the python-3 package. This is slightly ugly.
The solution with the wrapper has the advantage that users who want only
Python 3 and not Python 2 would then get a binary named "python" pointing
to version 3, useful also for their own code. But somewhere it would have
to be documented that they then have to install python-3-wrapper and not just
python or python-3.
But the naming is not very clear; why do I need to install python-wrapper
if I just want the latest version of Python?
How about calling the package python-default and having it contain python-3
as a propagated input? We could even have a version 2 of this package, which
would be empty with only python-2 as a propagated input. Then the user could:
- install python-default = python-default-3 and get only Python 3,
with binaries "python" and "pydoc" pointing to "python3" and "pydoc3",
respectively;
- install python-default-2 and get only Python 2.
- install python-2 and python = python-3 to get both of them, with
"python" pointing to Python 2.
What do you think?
Andreas
next prev parent reply other threads:[~2013-09-01 14:39 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
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 [this message]
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=20130901143907.GA23394@debian \
--to=andreas@enge.fr \
--cc=guix-devel@gnu.org \
--cc=ludo@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).