This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author r.david.murray
Recipients pgacv2, r.david.murray
Date 2017-02-23.15:51:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1487865071.95.0.343590599803.issue29632@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2017-02-23 15:51:11r.david.murraysetrecipients: + r.david.murray, pgacv2
2017-02-23 15:51:11r.david.murraysetmessageid: <1487865071.95.0.343590599803.issue29632@psf.upfronthosting.co.za>
2017-02-23 15:51:11r.david.murraylinkissue29632 messages
2017-02-23 15:51:11r.david.murraycreate