On 10/16/2013 01:52 PM, Tristan Seligmann wrote: > On Tue, Oct 15, 2013 at 1:47 PM, Thomas Goirand <z...@debian.org> wrote: >> On 10/15/2013 06:21 PM, Tristan Seligmann wrote: >>> What sort of upstream "source code" would be using the /usr/bin >>> wrapper at all? (I ask this question without prejudice; I can >>> obviously imagine some ways this might happen, but I'm more interested >>> in the actual existing use cases that you implied, not ones that only >>> exist in my imagination) >> >> I'm not sure if you're talking about the *full path* bit or what. >> Upstream code (or at least, unit tests...) is calling "coverage" from >> the standard accessible $PATH. >> >> For example: >> >> zigo@ ~/os/heat/heat heat (debian/havana)# cat tox.ini | grep coverage >> python setup.py testr --coverage > > Does this really invoke /usr/bin/coverage, as opposed to just > importing the coverage module (I'm not familiar with testrepository)?
Yes, please look at the beginning of #726255 where I show what happens. Thomas -- 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/525e423d.6000...@debian.org