Displaying 2 results from an estimated 2 matches for "situatoin".
Did you mean:
situation
2019 Dec 17
2
Python 2 compatibility for utility scripts
...n. But if it does, we can port it then, or else we might just
>> decide it's fine for it to be python3 only.
>>
>
> You don't see any advantage to having a consistent language level across
> the project? (See also the flang vs c++17 discussion.)
>
In this particular situatoin, correct. For these auxilliary scripts which
are not released or used to build/test released components, I see no
advantage to requiring these to support python2, anymore.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/at...
2019 Dec 17
2
Python 2 compatibility for utility scripts
It sounds like you ran into a bug in the test infrastructure's code to
determine if python3 is supported. Fixing that might be harder, but it only
needs to be fixed once no matter how much more python3 development there
will be.
Right now, most of our scripts were originally written for python 2, so
certainly it's easy for them to support python 2. But, it was a lot of work
by various