Bug#726255: Claiming ‘/usr/bin/coverage’ for a Python-specific programmer tool

2013-10-28 Thread Ben Finney
package python-coverage outlook 726255 The name ‘/usr/bin/coverage’ is too broad for so specific a tool. tags 726255 + wontfix thanks On 16-Oct-2013, Ben Finney wrote: > I'm glad we discussed this. I haven't seen a convincing argument that > overrides the consensus here that a Python-specific prog

Bug#726255: Claiming ‘/usr/bin/coverage’ for a Python-specific programmer tool

2013-10-16 Thread Thomas Goirand
On 10/16/2013 02:05 PM, Ben Finney wrote: > Thomas Goirand writes: > >> 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

Bug#726255: Claiming ‘/usr/bin/coverage’ for a Python-specific programmer tool

2013-10-15 Thread Ben Finney
Thomas Goirand writes: > On 10/16/2013 07:32 AM, Ben Finney wrote: > > Patching upstream's assumptions of command names is a feature of the > > landscape for Debian packagers. I don't consider that a reason to > > presume ‘/usr/bin/coverage’ on Debian should refer to a > > Python-specific tool. >

Bug#726255: Claiming ‘/usr/bin/coverage’ for a Python-specific programmer tool

2013-10-15 Thread Ben Finney
Tristan Seligmann writes: > Does this really invoke /usr/bin/coverage, as opposed to just > importing the coverage module (I'm not familiar with testrepository)? > I would have expected most Python tools to just import the module, > rather than spawning the wrapper as an external process, hence m

Bug#726255: Claiming ‘/usr/bin/coverage’ for a Python-specific programmer tool

2013-10-15 Thread Ben Finney
Thomas Goirand writes: > 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 act

Bug#726255: Claiming ‘/usr/bin/coverage’ for a Python-specific programmer tool

2013-10-15 Thread Ben Finney
Thomas Goirand writes: > 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 act

Bug#726255: Claiming ‘/usr/bin/coverage’ for a Python-specific programmer tool

2013-10-15 Thread Thomas Goirand
On 10/16/2013 07:32 AM, Ben Finney wrote: >> Nearly all OpenStack projects are using testrepository. All of them >> are using python-coverage. > > That sounds like an excellent central point to make the command name > parameterisable: fix it in one place to match the Debian > ‘python-coverage’ pac