Yaniv Aknin <yaniv.ak...@gmail.com> added the comment: I'm looking into making a patch from this for py3k, and have the following observations:
1. I agree with merwok, at the moment the monolithic ConfigureAction is a bit excessive for most uses (other than maybe emulating ./Configure...). I vote we split it to FlagAction and ConfigureAction. 2. I don't think this should be added as an argparse builtin/registered action (like action='store' or action='count'), but rather as a ready-made user-action in a separate namespace (from argparse.actions import FlagAction) Given feedback that these two decisions seem sane, I'd be happy to produce a patch against recent py3k. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue8538> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
