git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Python version auditing followup

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 20, 2012, 21:39 UTC
Message-ID
<7vzk182yka.fsf@alter.siamese.dyndns.org>
In-Reply-To
<kb001v$vps$1@ger.gmane.org>
"Joachim Schmitz" <jojo@schmitz-digital.de> writes:
Show 10 quoted lines
> Junio C Hamano wrote:
>> I personally would think 2.6 is recent enough.  Which platforms that
>> are long-term-maintained by their vendors still pin their Python at
>> 2.4.X?  2.4.6 was in 2008 that was source only, 2.4.4 was in late
>> 2006 that was the last 2.4 with binary release.
>>
>> Objections?  Comments?
>
> We have a working 2.4.2 for HP-NonStop and some major problems getting
> 2.7.3 to work.

I do not think a platform that stops at 2.4.2 instead of going to higher 2.4.X series deserves to be called "long term maintained by their vendors". It sounds more like "attempted to supply 2.4.X and abandoned the users once onee port was done" to me.

Previous: Joachim SchmitzNext: Joachim Schmitz
Message 4 of 9 in “Python version auditing followup”
  1. Eric S. RaymondDec 20, 2012
  2. Junio C HamanoDec 20, 2012
  3. Joachim SchmitzDec 20, 2012
  4. Junio C HamanoDec 20, 2012
  5. Joachim SchmitzDec 21, 2012
  6. Junio C HamanoDec 21, 2012
  7. Joachim SchmitzDec 21, 2012
  8. Junio C HamanoDec 21, 2012
  9. Dennis KaarsemakerDec 27, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.