Closed #212.
--
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#event-1082511411___
Rpm-maint mailing list
I think this is a lesson how thinking needs to be different between one
particular (or even all) distribution and rpm upstream. There is just no point
for rpm upstream to switch from one old thing to the new thing while everyone
else is also switching. This just complicates stuff for everyone.
I would say that there is no good patch, so distros would have to patch
something anyway, so I would close it as well.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
So seeing as no one has the resources to guide the larger patch, then unless
you find the simple shebang change acceptable, I suggest we close the issue.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
So, to conclude the discussion: I don't really have the know-how and time to
push through the more complicated change that @proyvind proposed. Would you be
interested in leading that, @proyvind ? I would help where I can.
--
You are receiving this because you are subscribed to this thread.
> As distros completes their migration to python 3 and no python 2 package
> installed on system, any py3k compatible script from packages in distro using
> /usr/bin/python as shebang will be left broken, for which there surely are
> quite a few.
That's exactly what you want and why Fedora,
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:
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
>> 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:
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
> 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
well, I think we should have some configure switch which interpreter to use for
all of python scripts... But this PR as it is a bit ugly..
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
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.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Conan-Kudo approved this pull request.
I don't have a problem with this.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
14 matches
Mail list logo
