Jason R. Coombs added the comment:
That's interesting that there's activity on this again. I had forgotten I'd
filed it. It's particularly timely, as I just yesterday had this experience
again. I looked at the documentation and found it inadequate for me to
understand how to implement a custom action, so I went to the source to figure
it out. The action I ended up creating was this one:
class SandboxAction(argparse.Action):
def __init__(self, *args, **kwargs):
super().__init__(*args, nargs=0, **kwargs)
def __call__(self, *args, **kwargs):
cls.use()
Where 'cls' is defined in the same scope where SandboxAction was defined. I'm
not sure if my documentation patch would have been sufficient to allow me to
write that Action without consulting the source, but this example represents
another case where that should be possible.
I haven't made any tweaks to the patch as a result of Steven's comments, so I
probably could do that. I don't now when I'll have the time to do that, but
I'll keep a tab to remind me to revisit the issue again.
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue13540>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
