Message288457
The obvious thing to do would be to make the Action subclasses have public names. I personally would continue to use the strings, though, as they are easier to type. (The same would be true if an enum were introduced (that I'd continue to use the stings because they are easier to type :), since they would need to be namespaced (argparse.action.store_true, for example).)
I can see some potential value in exposing the action subclasses, but I'm not sure if it is worth it. |
|
Date |
User |
Action |
Args |
2017-02-23 15:51:11 | r.david.murray | set | recipients:
+ r.david.murray, pgacv2 |
2017-02-23 15:51:11 | r.david.murray | set | messageid: <1487865071.95.0.343590599803.issue29632@psf.upfronthosting.co.za> |
2017-02-23 15:51:11 | r.david.murray | link | issue29632 messages |
2017-02-23 15:51:11 | r.david.murray | create | |
|