With preparation for multi-python-interpreters world we obsoleted the
%python3_only macro wrappers.
We switched most of the Tumbleweed uses to %python_alternative that
will allow us later to let users select which interpreter their
binaries should use.
Next on our map is to convert the interpreter to allow coinstall (we
will probably add 3.9 alpha or 3.6 back depending what we deem easier).
If you happen to have a new package that has the %python3_only, please
replace it, the same applies for existing packages if you spot it in
them (some might've moved to use %python3_only inbetween we started and
The wiki now also describes the %python3_only as deprecated and
recommends usage of %python_alternative with sample.
Of course nothing will break until we completely switch to the multi-
instances which will be months from now so even if you spot something
still using %python3_only there is no need to act upon it right now.
Show replies by date