But this section explicitly only covers the rare case where a py2
and
py3 version of something provide _different_ functionality.
The example spec is for the normal case. That's why it's up
above the
"Avoiding collisions between the python 2 and python 3 stacks" section.
That section covers a specific case which applies to only a few packages.
Well, here's what the guidelines say about the normal case:
"If the executables provide the same functionality independent of whether they are
run on top of Python 2 or Python 3, then only the Python 3 version of the executable
should be packaged."
Since the spec file does package both p2 and p3 versions of the executable, I infer that
we are indeed dealing with the case where it is beneficial to package both p2 and p3
version of the executable, in which case my first post applies and the example is wrong.
So in summary, either the example is wrong by packaging both p2 and p3 versions of the
executable, or it is wrong by packaging the p3 version of the executable as the default
one.