[libcxx-commits] [libcxx] [libc++] Use python3 in ssh.py's shebang (PR #183491)

[Lucas Chollet via libcxx-commits]

LucasChollet wrote:

@ldionne 

> Either way seems fine, but it seems to me that perhaps using whatever python version the user currently has in their environment should also work.

Python 2 EOL was in 2020 (first announced for 2015 in 2008). I also found a relevant comment in this [RFC](https://discourse.llvm.org/t/rfc-python-2-python-3-status/54340/6), saying that `python3` should be used.

> Is this patch fixing an issue for you, and if so, what is it?

`python` used to link to a Python 2 executable and some Linux distributions (like Debian and its derivatives) chose to stop providing a non-versioned `python` executable when dropping support for Python 2.
There is a python-is-python3 package to provide it, but it's not installed by default.
So on my Ubuntu box I get this error when running the script:
`/usr/bin/env: 'python': No such file or directory`



https://github.com/llvm/llvm-project/pull/183491