From: Brandon Invergo <brandon@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Python 3 binaries
Date: Mon, 02 Sep 2013 08:24:48 +0200 [thread overview]
Message-ID: <877gez91vz.fsf@naga.invergo.net> (raw)
In-Reply-To: <87k3j0igz8.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sun, 01 Sep 2013 19:34:03 +0200")
[-- Attachment #1: Type: text/plain, Size: 1065 bytes --]
ludo@gnu.org (Ludovic Courtès) writes:
> My understanding was that users (really: Python developers) would expect
> to get a ‘python3’ binary when they install the latest, and a ‘python’
> binary otherwise.
It depends. I've grown used to having python(->python3) and python2
binaries in Parabola/Arch, where it is the policy to always have the
latest version as the default.
> Then that means we don’t really have to worry, and just document that
> the python-3.x package is an unmodified upstream package, with its
> binary is called ‘python3’.
I think that is a fine way to do it. The most important part is
internal consistency. It seems that the "unmodified upstream" strategy
is the path of least resistance, and it will fit with the expectations
of all of the Debian-based users out there.
As for the shebangs, you may well still have to do some patching for
some packages, if they were written in python3 but the shebang is for
/usr/bin/python.
-brandon
--
Brandon Invergo
http://brandon.invergo.net
[-- Attachment #2: Type: application/pgp-signature, Size: 489 bytes --]
next prev parent reply other threads:[~2013-09-02 6:25 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
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 [this message]
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=877gez91vz.fsf@naga.invergo.net \
--to=brandon@gnu.org \
--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).