Evan

I just encountered this issue with Python 3.6.1 and `pip install git+git://github.com/smsearcy/bumpversion.git@issue-135` resolved it for me.

Perhaps this should only be supported if the function signature is overridden in the docstring as per [this example](http://stackoverflow.com/questions/12082570/override-function-declaration-in-autodoc-for-sphinx). As a side note, I should update `defopt.run` to do this.

Everything currently maps to the function signature so it's a bit of work to start adding extra parameters. Can look into this again if someone has a use case for...

`yamlize` makes me feel a little uneasy, since it puts the responsibility on the user to enter arguments in a particular way in order to get appropriate types, rather than...

I've been thinking about `filter_kwargs`, and I think the thing that worries me about it is it starts to stray beyond the capabilities of argparse, which I'd rather avoid if...

Possible design: ``` from common import config def main(...): ... defopt.run(main, setup=config) ``` When using a single command as above, arguments from `config` would be mixed with arguments for `main`...

Thanks for the detailed comments! I've just skimmed them for the moment but I'll come back and have a proper look in the next few days. I've opened #13 for...

The reason I initially didn't want to automatically pick short flags is that adding a parameter to any of the called functions could then unintentionally steal a short flag from...

Do you have some examples in mind for how this would be used and what the resulting command line would look like?

I think the main problem I have with zipping up the extra arguments into `**kwargs` is that it's difficult to emulate argument parsing in exactly the same way argparse does...