paul j3 added the comment: It'll take me a while to work through this proposed patch. My first reaction is that I am uncomfortable with adding an attribute to all parsers just to implement this help feature. For one thing it seems to cross functionality boundaries.
I need to review how subparser help is implemented. A lot of the work is done in the subparsers action itself, not the HelpFormatter. I have a vague memory of another bug issue involving this subparser help. I'll have to look it up. There are several bug issues related to formatting `choices`. In some cases they are too long to display properly. And this formatting adds an iterablity requirement. I worked on consolidating choices formatting into a separate method. In one version it was module level function, in another refactoring I made it an Action method. If it was an Action method, then the subparsers_action class could implement its own version. Another thought - the formatting of choices is closely linked to the metavar. Anyways, at this point I have a bunch of random thoughts that need research and organizing. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue22848> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
