> This makes no sense, /usr/bin/python is usually the linked to the binary of 
> the default python version in use on distros, so hardcoding the version makes 
> no sense.

That is a common misconception. While some distros went ahead and switched 
`/usr/bin/python` to Python 3, most notably Arch Linux, most are keeping it 
pointing to Python 2 and will continue to do so at least until Python 2 EOL in 
2020. Upstream Python issued a recommendation to that effect as well: [PEP 394 
-- The "python" Command on Unix-Like 
Systems](https://www.python.org/dev/peps/pep-0394/#abstract)

So while most distros that will be using the latest RPM already switched to 
Python 3 being default, the binary `/usr/bin/python` still points to Python 2. 
That means that most distros will need to patch this shebang to 
`/usr/bin/python3` before deploying.

I propose that we switch the shebang to explicitly Python 3 by default. There 
possibly might be some distros that will be using the latest RPM version but 
still haven't switched to Python 3 being default (and they will need to patch 
this shebang back to Python 2), but I'd wager it will be a minuscule number 
compared to Python 3–default distros.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/212#issuecomment-299131961
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint

Reply via email to