search for: d42450

...#!/usr/bin/python` (which is a symlink to python2.7 on many platforms) and some of them use Python 2 syntax that is not compatible with Python 3 (e.g. print statements; str/bytes) I created a revision to migrate utils/update_{llc_,}_test_checks.py from Python 2 to Python 3 https://reviews.llvm.org/D42450 , the arguments against making it Python 3 is: * There are many Mac OS X users and Mac OS X 10.8 comes with Python 2.7 pre-installed [0] but not Python 3. * Forcing scripts to use Python 3 (by doing so we can avoid some compatibility trouble) may not be a good idea. Python 2.7 was published in 20...

.../python` (which is a symlink to python2.7 on many platforms) and some of them use Python 2 syntax that is not compatible with Python 3 (e.g. print statements; str/bytes) > > I created a revision to migrate utils/update_{llc_,}_test_checks.py from Python 2 to Python 3 https://reviews.llvm.org/D42450 <https://reviews.llvm.org/D42450> , the arguments against making it Python 3 is: > > * There are many Mac OS X users and Mac OS X 10.8 comes with Python 2.7 pre-installed [0] but not Python 3. > * Forcing scripts to use Python 3 (by doing so we can avoid some compatibility trouble)...

...h is a symlink to python2.7 on many platforms) > and some of them use Python 2 syntax that is not compatible with Python 3 > (e.g. print statements; str/bytes) > > I created a revision to migrate utils/update_{llc_,}_test_checks.py from > Python 2 to Python 3 https://reviews.llvm.org/D42450 , the arguments > against making it Python 3 is: > > * There are many Mac OS X users and Mac OS X 10.8 comes with Python 2.7 > pre-installed [0] but not Python 3. > * Forcing scripts to use Python 3 (by doing so we can avoid some > compatibility trouble) may not be a good idea. &g...

...platforms) and some of them use Python 2 syntax that is not >> compatible with Python 3 (e.g. print statements; str/bytes) >> >> I created a revision to migrate >> utils/update_{llc_,}_test_checks.py from Python 2 to Python 3 >> https://reviews.llvm.org/D42450 <https://reviews.llvm.org/D42450> >> , the arguments against making it Python 3 is: >> >> * There are many Mac OS X users and Mac OS X 10.8 comes with >> Python 2.7 pre-installed [0] but not Python 3. >> * Forcing scripts to use Python 3 (by doing...

.../python` (which is a symlink to python2.7 on many platforms) and some of them use Python 2 syntax that is not compatible with Python 3 (e.g. print statements; str/bytes) > > I created a revision to migrate utils/update_{llc_,}_test_checks.py from Python 2 to Python 3 https://reviews.llvm.org/D42450 , the arguments against making it Python 3 is: > > * There are many Mac OS X users and Mac OS X 10.8 comes with Python 2.7 pre-installed [0] but not Python 3. > * Forcing scripts to use Python 3 (by doing so we can avoid some compatibility trouble) may not be a good idea. > > Pytho...

...(which is a symlink to python2.7 on many platforms) and some of them use Python 2 syntax that is not compatible with Python 3 (e.g. print statements; str/bytes) >> >> I created a revision to migrate utils/update_{llc_,}_test_checks.py from Python 2 to Python 3 https://reviews.llvm.org/D42450 , the arguments against making it Python 3 is: >> >> * There are many Mac OS X users and Mac OS X 10.8 comes with Python 2.7 pre-installed [0] but not Python 3. >> * Forcing scripts to use Python 3 (by doing so we can avoid some compatibility trouble) may not be a good idea. >...

...orms) >>> and some of them use Python 2 syntax that is not compatible with Python 3 >>> (e.g. print statements; str/bytes) >>> >>> I created a revision to migrate utils/update_{llc_,}_test_checks.py from >>> Python 2 to Python 3 https://reviews.llvm.org/D42450 , the arguments against >>> making it Python 3 is: >>> >>> * There are many Mac OS X users and Mac OS X 10.8 comes with Python 2.7 >>> pre-installed [0] but not Python 3. >>> * Forcing scripts to use Python 3 (by doing so we can avoid some >>>...

...thon2.7 on many platforms) >> and some of them use Python 2 syntax that is not compatible with Python 3 >> (e.g. print statements; str/bytes) >> >> I created a revision to migrate utils/update_{llc_,}_test_checks.py from >> Python 2 to Python 3 https://reviews.llvm.org/D42450 , the arguments against >> making it Python 3 is: >> >> * There are many Mac OS X users and Mac OS X 10.8 comes with Python 2.7 >> pre-installed [0] but not Python 3. >> * Forcing scripts to use Python 3 (by doing so we can avoid some >> compatibility trouble) ma...

...thon2.7 on many platforms) >> and some of them use Python 2 syntax that is not compatible with Python 3 >> (e.g. print statements; str/bytes) >> >> I created a revision to migrate utils/update_{llc_,}_test_checks.py from >> Python 2 to Python 3 https://reviews.llvm.org/D42450 , the arguments against >> making it Python 3 is: >> >> * There are many Mac OS X users and Mac OS X 10.8 comes with Python 2.7 >> pre-installed [0] but not Python 3. >> * Forcing scripts to use Python 3 (by doing so we can avoid some >> compatibility trouble) ma...

...t; and some of them use Python 2 syntax that is not compatible with Python 3 >>>> (e.g. print statements; str/bytes) >>>> >>>> I created a revision to migrate utils/update_{llc_,}_test_checks.py from >>>> Python 2 to Python 3 https://reviews.llvm.org/D42450 , the arguments against >>>> making it Python 3 is: >>>> >>>> * There are many Mac OS X users and Mac OS X 10.8 comes with Python 2.7 >>>> pre-installed [0] but not Python 3. >>>> * Forcing scripts to use Python 3 (by doing so we can avoi...

...orms) >>> and some of them use Python 2 syntax that is not compatible with Python 3 >>> (e.g. print statements; str/bytes) >>> >>> I created a revision to migrate utils/update_{llc_,}_test_checks.py from >>> Python 2 to Python 3 https://reviews.llvm.org/D42450 , the arguments against >>> making it Python 3 is: >>> >>> * There are many Mac OS X users and Mac OS X 10.8 comes with Python 2.7 >>> pre-installed [0] but not Python 3. >>> * Forcing scripts to use Python 3 (by doing so we can avoid some >>>...

...and some of them use Python 2 syntax that is not compatible with Python 3 > >>> (e.g. print statements; str/bytes) > >>> > >>> I created a revision to migrate utils/update_{llc_,}_test_checks.py from > >>> Python 2 to Python 3 https://reviews.llvm.org/D42450 <https://reviews.llvm.org/D42450> , the arguments against > >>> making it Python 3 is: > >>> > >>> * There are many Mac OS X users and Mac OS X 10.8 comes with Python 2.7 > >>> pre-installed [0] but not Python 3. > >>> * Forcing scri...

...f them use Python 2 syntax that is not compatible with > Python 3 > >>> (e.g. print statements; str/bytes) > >>> > >>> I created a revision to migrate utils/update_{llc_,}_test_checks.py > from > >>> Python 2 to Python 3 https://reviews.llvm.org/D42450 , the arguments > against > >>> making it Python 3 is: > >>> > >>> * There are many Mac OS X users and Mac OS X 10.8 comes with Python 2.7 > >>> pre-installed [0] but not Python 3. > >>> * Forcing scripts to use Python 3 (by doing so we...

...them use Python 2 syntax that is not compatible with Python 3 >>>>> (e.g. print statements; str/bytes) >>>>> >>>>> I created a revision to migrate utils/update_{llc_,}_test_checks.py from >>>>> Python 2 to Python 3 https://reviews.llvm.org/D42450 , the arguments against >>>>> making it Python 3 is: >>>>> >>>>> * There are many Mac OS X users and Mac OS X 10.8 comes with Python 2.7 >>>>> pre-installed [0] but not Python 3. >>>>> * Forcing scripts to use Python 3 (by d...

...f them use Python 2 syntax that is not compatible with > Python 3 > >>> (e.g. print statements; str/bytes) > >>> > >>> I created a revision to migrate utils/update_{llc_,}_test_checks.py > from > >>> Python 2 to Python 3 https://reviews.llvm.org/D42450 , the arguments > against > >>> making it Python 3 is: > >>> > >>> * There are many Mac OS X users and Mac OS X 10.8 comes with Python 2.7 > >>> pre-installed [0] but not Python 3. > >>> * Forcing scripts to use Python 3 (by doing so we...