On 7/8/19 2:42 PM, Matěj Cepl wrote:
On 2019-07-05, 07:04 GMT, you wrote:
How can things work for non-python3 when we have plenty of:
%python3_only %{_bindir}/foorun
in the %files sections? Or does "working" mean "build succeeds" ?
What’s wrong with %python3_only for files in %{_bindir}?
Logic behind this is usually: we have python2 compatible library for all python2 programs they need it, and if you need running command foorun, then you usually don’t care whether it uses python2 or python3 in the background, you just want to run it.
I *do* care. I don't want to install the whole python3 requirements just for running a command. And with all this %python3_only, commands will not work for python2 (which will die anyway) and pypy (the statement was that on pypy most things just work).
We can of course do alternatives for all those foorun commands, but it is usually too much bother, and I am really not sure what’s wrong with this logic.
That you can not run commands in py2/pypy-only environments. Best, Tom -- To unsubscribe, e-mail: opensuse-python+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-python+owner@opensuse.org