I think it's reasonable to get OpenStack to look for python-coverage to run it's tests when using a system package. Or use python -m coverage. 'coverage' is indeed super generic and the precedent within Debian for the package is to call the binary 'python-coverage'.
Is there some reason we can't take that approach? -Rob -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caj3hoz1ll-0ppj0khd2pw4fbn71bu+e9ouyuernui4mu2ss...@mail.gmail.com
