[PATCH] D82767: clang-format: Explicitly use python3

Matt Arsenault via Phabricator via cfe-commits cfe-commits at lists.llvm.org
Thu Jul 9 11:46:11 PDT 2020


arsenm added a comment.

In D82767#2141962 <https://reviews.llvm.org/D82767#2141962>, @serge-sans-paille wrote:

> In D82767#2132903 <https://reviews.llvm.org/D82767#2132903>, @MyDeveloperDay wrote:
>
> > We may not be consistent across all of LLVM
> >
> >   $ find . -name '*.py' -print -exec /usr/bin/head -2 {} \; | grep "#!" | sort | uniq -c
> >         6 #! /usr/bin/env python
> >         2 #! /usr/bin/env python3
> >         2 #! /usr/bin/python
> >         1 #!/bin/env python
> >       133 #!/usr/bin/env python
> >        13 #!/usr/bin/env python3
> >        49 #!/usr/bin/python
> >
>
>
> My understanding is that explicitly requiring python3 may make sense if the script is not backward-compatible with python2, while requiring python means the version is not important.
>  At the end-of-year, we should be able to harmonize shebangs to #!/usr/bin/env python3 or #!/usr/bin/env python


Fixing this to be consistent would be an improvement


CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D82767/new/

https://reviews.llvm.org/D82767





More information about the cfe-commits mailing list