The reason behind the second change is that there are a lot of Python 2
only packages having `python-xxx` in Requires, which will start pulling
Python 3 dependencies when we switch to Python 3 as default. This will
most possibly cause a number of unexpected issues, which is what we are
trying to avoid.
If you expect your package to work when we switch to Python 3 as
default, then you should already switch it to Python 3 or provide a
Python 3 subpackage and depend on `python3-xxx`.
Iryna
On 06/19/2017 04:11 PM, Tom Hughes wrote:
On 19/06/17 14:59, Iryna Shcherbina wrote:
Recently, there were two important changes to Python packaging
guidelines. The first one bans usingtheambiguous `python` prefix in
binary RPM package names [1]. Thus you must explicitly
definethePython version by using either `python2-` or `python3-`. The
second change bans depending on anything using the ambiguous
`python-` prefixed names in (Build)Requires [2].
I don't understand the logic behind the second change with regard to
Requires, or at least I think there are cases where it makes no sense.
If I have a package with a python script using #!/usr/bin/python and
importing xxx then isn't python-xxx the correct thing to require so
that it will continue to behave correctly when we switch to python 3
as default?
If I change it to python2-xxx then I'll just have to change it again
when we switch the default?
Tom
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
