Message105620
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. |
|
Date |
User |
Action |
Args |
2010-05-13 01:01:22 | Yaniv.Aknin | set | recipients:
+ Yaniv.Aknin, bethard, eric.smith, eric.araujo |
2010-05-13 01:01:22 | Yaniv.Aknin | set | messageid: <1273712482.52.0.969762266608.issue8538@psf.upfronthosting.co.za> |
2010-05-13 01:01:20 | Yaniv.Aknin | link | issue8538 messages |
2010-05-13 01:01:18 | Yaniv.Aknin | create | |
|