http://llvm.org/docs/GettingStarted.html currently mentions Python 2.5 as a minimum required version. I'd like to use argparse <https://docs.python.org/dev/library/argparse.html> in a script and be able to test this script. This requires Python 2.7. This version has been around since 2010, and afaiu, is available on all modern platforms. Is there any reason not to change minimum required version of Python to 2.7? -- Regards, Alexander Kornienko -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20140626/d229512d/attachment.html>
AFAIK, 2.5 is minimum for running automated tests with lit. If your script does not run as part of lit, you are less constrained. For instans, utils/sort_includes.py uses argparse Eli On Wed, Jun 25, 2014 at 5:11 PM, Alexander Kornienko <alexfh at google.com> wrote:> http://llvm.org/docs/GettingStarted.html currently mentions Python 2.5 as > a minimum required version. I'd like to use argparse > <https://docs.python.org/dev/library/argparse.html> in a script and be > able to test this script. This requires Python 2.7. This version has been > around since 2010, and afaiu, is available on all modern platforms. Is > there any reason not to change minimum required version of Python to 2.7? > > -- > Regards, > Alexander Kornienko > > _______________________________________________ > 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/20140625/7553d64e/attachment.html>
As much as I like killing support for Python 2.6 and below, RHEL is usually the blocker. They still have 2.4 under support. Only the RHEL that was released a few weeks ago finally has 2.7.> On Jun 25, 2014, at 17:11, Alexander Kornienko <alexfh at google.com> wrote: > > http://llvm.org/docs/GettingStarted.html currently mentions Python 2.5 as a minimum required version. I'd like to use argparse in a script and be able to test this script. This requires Python 2.7. This version has been around since 2010, and afaiu, is available on all modern platforms. Is there any reason not to change minimum required version of Python to 2.7? > > -- > Regards, > Alexander Kornienko > _______________________________________________ > 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/20140625/dd2ebe1e/attachment.html>
Yeah, RHEL... Then I'm going to add a lit feature (say, python27) to guard the test of my python script on it with REQUIRES:. On Thu, Jun 26, 2014 at 2:52 AM, Gregory Szorc <gregory.szorc at gmail.com> wrote:> As much as I like killing support for Python 2.6 and below, RHEL is > usually the blocker. They still have 2.4 under support. Only the RHEL that > was released a few weeks ago finally has 2.7. > > On Jun 25, 2014, at 17:11, Alexander Kornienko <alexfh at google.com> wrote: > > http://llvm.org/docs/GettingStarted.html currently mentions Python 2.5 as > a minimum required version. I'd like to use argparse > <https://docs.python.org/dev/library/argparse.html> in a script and be > able to test this script. This requires Python 2.7. This version has been > around since 2010, and afaiu, is available on all modern platforms. Is > there any reason not to change minimum required version of Python to 2.7? > > -- > Regards, > Alexander Kornienko > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20140626/c371a457/attachment.html>
On Wed, Jun 25, 2014 at 5:52 PM, Gregory Szorc <gregory.szorc at gmail.com> wrote:> As much as I like killing support for Python 2.6 and below, RHEL is > usually the blocker. They still have 2.4 under support. Only the RHEL that > was released a few weeks ago finally has 2.7. >Given the amount of complexity required to build LLVM & Clang (having the right compiler & libstdc++ installed), compared to the 3 minutes it typically takes to install any Python version on any Linux box, these limitations always strike me as silly. But I gave up on this fight some time ago. Eli> > On Jun 25, 2014, at 17:11, Alexander Kornienko <alexfh at google.com> wrote: > > http://llvm.org/docs/GettingStarted.html currently mentions Python 2.5 as > a minimum required version. I'd like to use argparse > <https://docs.python.org/dev/library/argparse.html> in a script and be > able to test this script. This requires Python 2.7. This version has been > around since 2010, and afaiu, is available on all modern platforms. Is > there any reason not to change minimum required version of Python to 2.7? > > -- > Regards, > Alexander Kornienko > > _______________________________________________ > > 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/20140626/131caf66/attachment.html>
Reasonably Related Threads
- [LLVMdev] Python version requirement for LLVM
- Documentation doesn't get updated
- [LLVMdev] [llvm-commits] PROPOSAL: LLVM_FALLTHROUGH macro for intended fall-throughs between switch cases
- Missing clang-modernize in 3.8 (Debian 8 Jessie)
- [LLVMdev] [llvm-commits] PROPOSAL: LLVM_FALLTHROUGH macro for intended fall-throughs between switch cases