https://bugzilla.redhat.com/show_bug.cgi?id=1611829
--- Comment #24 from Robert-André Mauchin <zebob.m(a)gmail.com> ---
(In reply to Stefan Berger from comment #21)
(In reply to Robert-André Mauchin from comment #18)
> > python3 doesn't seem to create the symlink of python to the python3
executable. > So I have to use python2.
> > Actually, I need python as well. It seems to be the one setting the symlink. I
> > suppose it will set a different symlink once python3 takes over?
>
> Actually you must not use the "python" executable in your build script,
it
> is a warning since F28, and an error on F30. You should fix whatever part of
> your buildsystem that use "python" and make it use "python3".
>
If I follow the logic in this python specification then python is the
generic executable for programs running with python2 or python3.
https://www.python.org/dev/peps/pep-0394/
That's not the policy in Fedora:
https://fedoraproject.org/wiki/Packaging:Python#Multiple_Python_Runtimes
Packages in Fedora MUST NOT use /usr/bin/python. Instead packages for Python 3
MUST use /usr/bin/python3 (even if upstream supports both Python 2 and 3). As a
result of that /usr/bin/python (as well as /usr/bin/env python and similar)
MUST NOT be used in shebang lines or as a dependency of a package. As of Fedora
30, all uses of unversioned python executables in shebang lines will fail the
build. These shebangs MUST be fixed. If it is necessary to disable the checks,
please see the information in Packaging:Guidelines#Shebang_lines.
With the logic the 'provides' python and python-twisted are
virtual provides
in the python2 and python2-twisted packages that will be moved into python3
and python3-twisted at some point. So I doubt that python and python-twisted
will go away, they will just move to another package, and should be usable
by python version independent programs (which is what we have).
I am the maintainer of python-twisted, there won't be any provides for
python-twisted in F29 and F30, the large list of provides was due to a rename
years ago.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component