From: esr@thyrsus.com (Eric S. Raymond)
To: git@vger.kernel.org
Subject: Python version auditing followup
Date: Thu, 20 Dec 2012 09:34:11 -0500 (EST) [thread overview]
Message-ID: <20121220143411.BEA0744105@snark.thyrsus.com> (raw)
Most of the Python scripts in the distribution are small and simple to
audit, so I am pretty sure of the results. The only place where I
have a concern is the git_helpers library; that is somewhat more
complex and I might have missed a dependency somewhere. Whoever
owns that should check my finding that it should run under 2.4
That was the first of three patches I have promised. In order to do
the next one, which will be a development guidelines recommend
compatibility back to some specific version X, I need a policy
decision. How do we set X?
I don't think X can be < 2.4, nor does it need to be - 2.4 came out
in 2004 and eight years is plenty of deployment time.
The later we set it, the more convenient for developers. But of
course by setting it late we trade away some portability to
older systems.
In previous discussion of this issue I recommended X = 2.6.
That is still my recommendation. Thoughts, comments, objections?
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
In recent years it has been suggested that the Second Amendment
protects the "collective" right of states to maintain militias, while
it does not protect the right of "the people" to keep and bear arms.
If anyone entertained this notion in the period during which the
Constitution and the Bill of Rights were debated and ratified, it
remains one of the most closely guarded secrets of the eighteenth
century, for no known writing surviving from the period between 1787
and 1791 states such a thesis.
-- Stephen P. Halbrook, "That Every Man Be Armed", 1984
next reply other threads:[~2012-12-20 14:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-20 14:34 Eric S. Raymond [this message]
2012-12-20 18:30 ` Python version auditing followup Junio C Hamano
2012-12-20 21:30 ` Joachim Schmitz
2012-12-20 21:39 ` Junio C Hamano
2012-12-21 7:26 ` Joachim Schmitz
2012-12-21 18:28 ` Junio C Hamano
2012-12-21 18:44 ` Joachim Schmitz
2012-12-21 18:48 ` Junio C Hamano
2012-12-27 21:57 ` Dennis Kaarsemaker
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=20121220143411.BEA0744105@snark.thyrsus.com \
--to=esr@thyrsus.com \
--cc=git@vger.kernel.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.
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).