From: "Eric S. Raymond" <esr@thyrsus.com>
To: Michael Haggerty <mhagger@alum.mit.edu>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] Third try at documenting command integration requirements.
Date: Tue, 27 Nov 2012 12:56:19 -0500 [thread overview]
Message-ID: <20121127175618.GA11845@thyrsus.com> (raw)
In-Reply-To: <50B4A8E1.7050801@alum.mit.edu>
Michael Haggerty <mhagger@alum.mit.edu>:
> OK, now let's discuss *which* minimum Python version that git should
> support in the hypothetical new world...
By all means!
> It would be a shame to leave RHEL 5 users behind if Python is used to
> implement important git functionality. Python 2.4 is missing some of
> Python's shiny new features, but still quite OK. What features would
> you miss the most if we were to target Python 2.4 instead of 2.6?
Off the top of my head...the 'with' statement, the conditional
expression, and built-in JSON support. Other developers would be
likely to kick about the string format() method; personally I'm
cheerfully old-school about that.
I agree that 2.4 is still quite OK. I'm a little concerned that dropping that
far back might store up some transition problems for the day we decide to
make the jump to Python 3.
On the other hand, I think gating features on RHEL5 might be
excessively cautious. According to [1], RHEL will red-zone within 30
days if it hasn't done so already ([1] says "Q4"). And RHEL6 (with
Python 2.6) has been shipping for two years.
Policy suggestion: we aim to stay friendly for every version of RHEL that
is still in Support 1. I doubt anyone will code anything critical
in Python before Dec 31st - I'm certainly not planning to!
[1] http://en.wikipedia.org/wiki/Red_Hat_Enterprise_Linux RHEL5 is going
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
next prev parent reply other threads:[~2012-11-27 17:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-26 5:35 [PATCH] Third try at documenting command integration requirements Eric S. Raymond
2012-11-26 8:07 ` Perry Hutchison
2012-11-26 20:01 ` Junio C Hamano
2012-11-26 21:41 ` Eric S. Raymond
2012-11-27 11:49 ` Michael Haggerty
2012-11-27 17:56 ` Eric S. Raymond [this message]
2012-11-28 1:58 ` Junio C Hamano
2012-11-28 3:36 ` Eric S. Raymond
2012-11-26 21:41 ` Junio C Hamano
2012-11-26 22:01 ` Eric S. Raymond
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=20121127175618.GA11845@thyrsus.com \
--to=esr@thyrsus.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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).