This has executables in /usr/bin/ so it would be best to do something like:

build      : |
    %python3_setup
    %python_setup

install    : |
    %python3_install
    for _f in $installdir/usr/bin/*; do
      mv -v $_f ${_f}3
    done
    %python_install

to ensure that executables are retained for both python 2 and python 3.

The installer handles this. I could replace some of the files by symbolic links though...

build@solus-budgie ~/YPKG/root/python-coverage/install/usr/bin $ ls -l
total 20
-rwxr-xr-x 1 build build 387 Dec 30 18:10 coverage
-rwxr-xr-x 1 build build 397 Dec 30 18:10 coverage-2.7
-rwxr-xr-x 1 build build 395 Dec 30 18:10 coverage-3.5
-rwxr-xr-x 1 build build 391 Dec 30 18:10 coverage2
-rwxr-xr-x 1 build build 389 Dec 30 18:10 coverage3

Thanks for that, I think we should try and be as consistent as possible with the executable names across packages, so I always try to go for x and x3 for example. I'm sure you'll have seen there's been much discussion over what should be standard. Also it's interesting that it's handled by the install script in this case, I've only ever seen that with one other python package, I'd just assumed that it wasn't, sorry about that!