New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Better option, config file, help text, and plugin handling #36

Open

jpellerin opened this issue Dec 14, 2011 · 0 comments

Assignees

Member

jpellerin commented Dec 14, 2011

All related to option parsing.

The help text is insanely long. It should be more like hg's, with basic
help as the default, and help for plugins requiring an additional arg.
The --where option doesn't work correctly. It doesn't, for instance,
result in nose picking up setup.cfg in the target directory
It should be possible to add plugins to the available set with a
commandline/config file argument (--plugin=package.module.Plugin?)

All of those require a substantially different option parser than the default:

Must be able to process args in stages (pull out --where, pull out
--plugin, then process the rest)
Must have more flexible help output

Google Code Info:
Issue #: 271
Author: [email protected]
Created On: 2009-06-03T20:17:55.000Z
Closed On:

ghost assigned jpellerin

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment