> 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
I do not see any possibility how to define sensible syntax of the triple
operator, without possible causing problems for macros %{?condition:true} and
%{!?condition:false}. Thus I think that adding this macro without additional
changes is not a good idea.
The syntax of the macro should start
First of all, while PEP 394 recommends this, it's not what's common practice
amongst distros, where Arch not even being a RPM based distro makes it less
relevant.
I know of no rpm based distros where /usr/bin/python isn't pointing to the
default python interpreter binary version. Also using
>> Welcome back to 2017, Mandriva is dead ;)
> Ah, that explains it :)
Mageia is still here, and we follow PEP 394.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
OpenMandriva uses python 3 as default, with /usr/bin/python pointing to python3.
AFAIK Mageia doesn't intentionally follow PEP 394 as much as it rather hasn't
switched to python3 as it's default yet, where ie. python packages prefixed
with python- are python 2, while python 3 packages are
the philosophical discussion regarding is anyways rather moot, but the patch
from my earlier comment should anyways be sufficient to address it properly. :)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
