package python-coverage tags 728824 + moreinfo thanks [Re-sending with the correct bug report number.]
On 29-Oct-2013, Ben Finney wrote: > On 28-Oct-2013, Barry Warsaw wrote: > > At the very least, I think there should be some way of hinting to users > > that run `coverage` that `python-coverage` or `python3-coverage` is the > > command. Maybe command-not-found will save us here? > > The documentation for ‘command-not-found’ suggests that it gets its > information from available packages, and suggests one to install. How > does that help us if the ‘python-coverage’ package is already installed? > > Moreover, I don't see how to inform ‘command-not-found’ of what we want. > The documentation doesn't imply any means of explicitly specifying this > information. This bug report needs a concrete proposal for how this package can reasonably install a configuration file that will cause a command-not-found event to suggest “Use ‘python-coverage’ instead”, in a way that will work for users by default. -- \ “I object to doing things that computers can do.” —Olin Shivers | `\ | _o__) | Ben Finney <[email protected]> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
