search for: 20000th

...o, ISTM that unfortunately, the decision to require python3 for is still premature, even some 10 years after its initial release. (Whether that state of the world is ridiculous, or whose fault that is, is irrelevant here; anyone who wants to have that discussion can go have it on python-dev for the 20000th time.) That said, I do think it could make sense to prepare llvm for the world in which "python" is python3 on some systems. So, I'd propose the following: 1. Change all #! lines to say "#!/usr/bin/env python2.7" instead of "#!/usr/bin/env python", if they only wo...

...o, ISTM that unfortunately, the decision to require python3 for is still premature, even some 10 years after its initial release. (Whether that state of the world is ridiculous, or whose fault that is, is irrelevant here; anyone who wants to have that discussion can go have it on python-dev for the 20000th time.) That said, I do think it could make sense to prepare llvm for the world in which "python" is python3 on some systems. So, I'd propose the following: 1. Change all #! lines to say "#!/usr/bin/env python2.7" instead of "#!/usr/bin/env python", if they only wo...

...o, ISTM that unfortunately, the decision to require python3 for is still premature, even some 10 years after its initial release. (Whether that state of the world is ridiculous, or whose fault that is, is irrelevant here; anyone who wants to have that discussion can go have it on python-dev for the 20000th time.) > > That said, I do think it could make sense to prepare llvm for the world in which "python" is python3 on some systems. So, I'd propose the following: > 1. Change all #! lines to say "#!/usr/bin/env python2.7" instead of "#!/usr/bin/env python",...

You might want to tell that to the Prominent North American Enterprise Linux Vendor that everybody is using... :) -Dimitry > On 1 Feb 2018, at 06:28, Tim Northover via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Since we seem to be voting, I'll -1 it. It's pretty ridiculous to have > a system without Python 3 in 2018 and anyone supplying such a > monstrosity

Since we seem to be voting, I'll -1 it. It's pretty ridiculous to have a system without Python 3 in 2018 and anyone supplying such a monstrosity should be encouraged to stop it. Tim. On 1 February 2018 at 05:20, Philip Reames via llvm-dev <llvm-dev at lists.llvm.org> wrote: > +1 to what Chris and Justin said. > > I see no strong benefit to moving to python3 and substantial

...ially fit the first 10000 observations, then the seq results in just the value 10000 which means that you do the update based on vaues 10001 through 20000, if xx only has 10000 rows, then this should give at least one error.  If xx has 20000 or more rows, then only chunksize 10000 will ever see the 20000th value, the other chunksizes will use less of the data. Understood your point and apologize that you had to spend time going into the logic inside for loop. I definitely thought of that but my actual problem was the variation in AICs (which I was sure about), so to ignore this loop problem (temporar...