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 -- Tom Hughes (tom@xxxxxxxxxx) http://compton.nu/ _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
