From: Jed Brown <jed@59A2.org>
To: Ramkumar Ramachandra <artagnon@gmail.com>,
Michael Haggerty <mhagger@alum.mit.edu>
Cc: Git List <git@vger.kernel.org>
Subject: Re: Review of git multimail
Date: Wed, 03 Jul 2013 16:09:52 -0500 [thread overview]
Message-ID: <87ppuzz6xr.fsf@mcs.anl.gov> (raw)
In-Reply-To: <CALkWK0=taYiV3UTaj9r-FLdaCeZRzVBTp_MH4sQt8-v+YYqbaA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1409 bytes --]
Ramkumar Ramachandra <artagnon@gmail.com> writes:
> Yeah, this is good reasoning. And yes, I'm on Arch: python points to
> python3, and python2 points to python2.
I'm also on Arch and it has been this way since October 2010 [1].
Ubuntu plans to remove python2 from the desktop CD images in 14.04 [2],
so having code that does not work with python3 will become more painful
pretty soon.
Note that RHEL5 has only python2.4 and will be supported through March,
2017. Since it is not feasible to have code that works in both python3
and any versions prior to python2.6, any chosen dialect will be broken
by default on some major distributions that still have full vendor
support.
> A couple of thoughts while we're on the subject:
>
> 1. We should probably convert git-remote-{hg,bzr} to use this style
> too:
Python-2.6.8 from python.org installs only python2.6 and python, but not
python2, so this will break on a lot of older systems. Some
distributions have been nice enough to provide python2 symlinks anyway.
Michael's rationale that at least the error message is obvious still
stands.
> Debian uses an alternatives mechanism to have multiple versions of the
> same package
Alternatives is global configuration that doesn't really solve this
problem anyway.
[1] https://www.archlinux.org/news/python-is-now-python-3/
[2] https://wiki.ubuntu.com/Python/3
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2013-07-03 21:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-02 19:23 Review of git multimail Ramkumar Ramachandra
2013-07-02 20:51 ` John Keeping
2013-07-02 21:34 ` Ramkumar Ramachandra
2013-07-02 22:21 ` Junio C Hamano
2013-07-03 8:02 ` Michael Haggerty
2013-07-03 8:16 ` Junio C Hamano
2013-07-03 8:29 ` John Keeping
2013-07-03 8:33 ` John Keeping
2013-07-03 0:10 ` Michael Haggerty
2013-07-03 10:23 ` Ramkumar Ramachandra
2013-07-03 11:02 ` Ramkumar Ramachandra
2013-07-03 11:41 ` Michael Haggerty
2013-07-03 21:09 ` Jed Brown [this message]
2013-07-04 8:11 ` Matthieu Moy
2013-07-04 8:27 ` Michael Haggerty
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=87ppuzz6xr.fsf@mcs.anl.gov \
--to=jed@59a2.org \
--cc=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=mhagger@alum.mit.edu \
/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.
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 NNTP newsgroup(s).