Hi all, On Tue, Oct 15, 2013 at 7:08 AM, Thomas Goirand <z...@debian.org> wrote: > Though, #726255 still needs a resolution, and I would like to have the > view of other Python module maintainers. Is using update-alternatives > the way to go? Was my commit correct? Is there any other (better) way to > do things here?
I agree with Thomas here. Update-alternatives is a good and standard way to do such things. For example, we use it in sphinx and python-docutils to provide tools like sphinx-build or rst2html. However, I don't agree with giving this bug grave severity. There are lots of ways to invoke coverage, i.e. using it from python, or using existing scripts. -- Dmitry Shachnev -- 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/CAKimPHWupd6mF6GFzOgnQyQED4AR6knFg9q2YRGt=v0y4on...@mail.gmail.com
