On Sun, 25 Oct 2015 18:27:50 +1100, Ben Finney wrote:
> Are you saying ‘dh_python3’ has done the wrong thing for this package?
>
> The Python 3.4 → 3.5 transition is currently underway in Sid, and
> presumably ‘dh_python3’ sets dependencies accordingly. Does that
> explain what you're seeing?

Quoting myself from 
https://lists.debian.org/debian-python/2015/10/msg00407.html:

  I think this is intended because:

    $ head -n1 </usr/bin/python3.4-coverage 
    #!/usr/bin/python3.4
    $ head -n1 </usr/bin/python3.5-coverage 
    #!/usr/bin/python3.5

  Looks like coverage supports being invoked as “python3.x -m coverage”, so 
there
  is no point in shipping per-Python-version scripts (having one script named
  python3-coverage will be enough).

--
Dmitry Shachnev

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to