I don't remember what I needed that for, now. Heh.
BTW, Glitter? https://xkcd.com/1810/
I thought you were pointing out a typo for a second, haha
Also, this happened: https://github.com/google/python-fire
Well, I started using Clize after I stopped doing my own one with docstringargs
(which is still on PyPI, but I'm not doing anything with it)
must be 'argh'
@epsy (and/or others) - I'm trying to write a program using the
attr library (https://attrs.readthedocs.io) and clize in concert with each other... is this possible? I'm at the beginning of combining usage of these two.
I noticed you also have an
attr module inside clize. Looking into using that instead. Does it also remove the need for the many "dunder" methods?
As for your initial question, Clize and attrs don't interfere with eachother, though there isn't specific support between eachother
I've been using attrs in conjunction with argument decorators at work, I intend to add an integration for this usecase in the future
if you use attrs in your project though, I recommend you depend on it directly, it's usually not a good idea to have implicit dependencies gotten from your dependencies' dependencies :)
Yes @r.barnes, you can annotate the parameters with
Parameter.IGNORE or Parameter.I and clize will skip them completely http://clize.readthedocs.io/en/stable/reference.html#skipping-parameters
Sorry, that was for @r-barnes
If you want to avoid annotations, you can use the
@sigtools.annotate(paramname=Parameter.I) decorator or wrap your function in a way that "masks" the parameters you want to make non-clized
@epsy, Mypy check Clize syntax as wrong. If you want to reply Guido Van Rossum, please, look python/mypy#5541. Thanks.
@epsy it would be great if you could point me to info on achieving sth equivalent to https://docs.python.org/3/library/argparse.html#argparse.ArgumentParser.parse_known_args
I'm writing a wrapper to pytest and want to allow users to pass arbitrary flag to pytest when they need them