[LLVMdev] Minimum Python Version

David Tweed David.Tweed at arm.com
Mon Dec 3 04:15:14 PST 2012

Note that RedHat Enterprise Linux has _very_ long dates to end-of-extended-life-cycle


RHEL4 has E-EOL of 2015, while RHEL5 has E-EOL of 2020. IIRC last time I checked Centos had a similarly long lifecycle.

This is just a piece of evidence about how long some distributions will be "supported". (I looked this up after I accidentally submitted a patch which used post Python-2.4 features that people pointed out broke stuff.)


-----Original Message-----
From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Dimitry Andric
Sent: 01 December 2012 22:08
To: Gregory Szorc
Cc: llvmdev at cs.uiuc.edu
Subject: Re: [LLVMdev] Minimum Python Version

On 2012-12-01 21:57, Gregory Szorc wrote:
> I'd like to continue the discussion about minimum Python versions from the "Use multiprocessing instead of threading" thread in its own thread because I feel it warrants additional discussion.
> For these reasons, I urge LLVM to drop support for Python older than 2.6. I would encourage requiring 2.7 (preferably the latest available release - 2.7.3 at this time) at the earliest convenience, but I'm not explicitly asking for it. While continued support for older Pythons is a noble goal and may continue to support people clinging to ancient Python releases, this will only make the path forward more difficult, as it puts an additional burden on those maintaining Python in the tree.

That is all well and good, but please be reminded there are zillions of Red Hat (or CentOS) users out there, stuck with either Python 2.5 or 2.6, who cannot easily upgrade without busting their whole system...
LLVM Developers mailing list
LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu

More information about the llvm-dev mailing list