Antony Lee

I guess what you can do right now is something like ```python from typing import Literal class Command: cmd: Literal["foo", "bar"] x: int y: float def __init__(self, cmd, *, x,...

The case of teardown can also be handled by an atexit handler (although again you'd need globals to pass things around -- but once you're architecting your module for CLI...

Adding an unknown_args_handler as suggested in https://github.com/anntzer/defopt/issues/7#issuecomment-233028244 seems reasonable, e.g. along the lines of ``` --- i/lib/defopt.py +++ w/lib/defopt.py @@ -154,7 +154,11 @@ def run(funcs: Union[Callable, List[Callable]], *, show_defaults=show_defaults, show_types=show_types,...

Something like ``` syntax region cppSTLscoped start='\(std\)\@3

The main problem I have with color_coded (and other similar tools) is the need to maintain a `.color_coded` file. My use case is often python extension modules, where the build...

It does not support setuptools (https://github.com/rdnetto/YCM-Generator#requirements-and-limitations). Even if I were to write it manually, .color_coded is necessarily a static list of flags, which is not sufficient (pkg-config actually returns different...

From a quick look, all the compiler-based projects suffer from the same issue (already mentioned above): they require a static list of compile flags (which may or may not be...

Does argcomplete currently support global installation with zsh? I haven't managed to get it to work (while it works fine with zsh), and I don't think this is clearly specified...

Yes, that is what I tried. I understand fixing this is not a priority for you but can you please document this limitation?

Similar issue: having an argument whose name starts with an underscore crashes argh (because it tries to pass "--" / "---foo" to argparse). I think this could be instead a...