Currently lit on windows will not work with python 3 because the internal shell has code like except OSError, e: and in python 3 one has to use except OSError as e: But that only works on python 2.6 and newer. So the question is: any objections to dropping support for python 2.5? Python 2.6 was released 01-Oct-2008, so it should be available everywhere. Cheers, Rafael
Adding Daniel. On Thu Dec 11 2014 at 11:53:42 AM Rafael Espíndola < rafael.espindola at gmail.com> wrote:> Currently lit on windows will not work with python 3 because the > internal shell has code like > > except OSError, e: > > and in python 3 one has to use > > except OSError as e: > > But that only works on python 2.6 and newer. > > So the question is: any objections to dropping support for python 2.5? > Python 2.6 was released 01-Oct-2008, so it should be available > everywhere. > > Cheers, > Rafael > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20141211/fe065ffe/attachment.html>
+1 I guess the only question is "who is using < 2.6 ?" -- Sean Silva On Thu, Dec 11, 2014 at 11:49 AM, Rafael Espíndola < rafael.espindola at gmail.com> wrote:> > Currently lit on windows will not work with python 3 because the > internal shell has code like > > except OSError, e: > > and in python 3 one has to use > > except OSError as e: > > But that only works on python 2.6 and newer. > > So the question is: any objections to dropping support for python 2.5? > Python 2.6 was released 01-Oct-2008, so it should be available > everywhere. > > Cheers, > Rafael > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20141211/5d346b29/attachment.html>
I'm all for… Trying to require 2.7 if possible? :-) Since we're bumping the req, we might as well bump as far as we can. That way we can also remove some compatibility things from (at least) lldb. (I haven't even tried 2.6 in a while, so it might not work due to other changes) Filipe On Thu, Dec 11, 2014 at 4:28 PM, Sean Silva <chisophugis at gmail.com> wrote:> +1 > > I guess the only question is "who is using < 2.6 ?" > > -- Sean Silva > > On Thu, Dec 11, 2014 at 11:49 AM, Rafael Espíndola < > rafael.espindola at gmail.com> wrote: >> >> Currently lit on windows will not work with python 3 because the >> internal shell has code like >> >> except OSError, e: >> >> and in python 3 one has to use >> >> except OSError as e: >> >> But that only works on python 2.6 and newer. >> >> So the question is: any objections to dropping support for python 2.5? >> Python 2.6 was released 01-Oct-2008, so it should be available >> everywhere. >> >> Cheers, >> Rafael >> _______________________________________________ >> LLVM Developers mailing list >> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >> > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20141211/da6afb9a/attachment.html>
RHEL 6 and variants (CentOS) ship with Python 2.4. RHEL 6 is in extended support for a few more years. I believe I've previously proposed a 2.7 migration on this list. A lot of people came out of the woodwork to object. Good luck moving forward. The world is better if Python <2.7 can be dropped.> On Dec 11, 2014, at 18:28, Sean Silva <chisophugis at gmail.com> wrote: > > +1 > > I guess the only question is "who is using < 2.6 ?" > > -- Sean Silva > >> On Thu, Dec 11, 2014 at 11:49 AM, Rafael Espíndola <rafael.espindola at gmail.com> wrote: >> Currently lit on windows will not work with python 3 because the >> internal shell has code like >> >> except OSError, e: >> >> and in python 3 one has to use >> >> except OSError as e: >> >> But that only works on python 2.6 and newer. >> >> So the question is: any objections to dropping support for python 2.5? >> Python 2.6 was released 01-Oct-2008, so it should be available >> everywhere. >> >> Cheers, >> Rafael >> _______________________________________________ >> LLVM Developers mailing list >> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20141211/d3d38d98/attachment.html>
+1 My view on this is that lit is a testing tool. If someone is competent enough to build LLVM and run the tests then they're probably competent enough to build a newer version of Python if for some reason they can't obtain pre-built version. I use lit outside of LLVM for several projects but I always use Python>= 2.7 so it's not a problem for me.I'd also be in favour of bumping the required version higher and require 2.7
So far two bots have complained about 2.7 (but have 2.6): http://bb.pgr.jp/builders/clang-i686-cygwin-RA-centos6/builds/12836/steps/configure/logs/stdio http://lab.llvm.org:8011/builders/llvm-s390x-linux1/builds/12002/steps/configure/logs/stdio Should we just upgrade those bots or reduce the requirement to 2.6? On 12 December 2014 at 06:41, Dan Liew <dan at su-root.co.uk> wrote:> +1 > > My view on this is that lit is a testing tool. If someone is competent > enough to build LLVM and run the tests then they're probably competent > enough to build a newer version of Python if for some reason they > can't obtain pre-built version. > > I use lit outside of LLVM for several projects but I always use Python >>= 2.7 so it's not a problem for me. > > I'd also be in favour of bumping the required version higher and require 2.7