Message103895
| Author |
gruszczy |
| Recipients |
andybuckley, bethard, eric.araujo, gruszczy, r.david.murray, wplappert |
| Date |
2010年04月21日.19:29:51 |
| SpamBayes Score |
2.0525487e-10 |
| Marked as misclassified |
No |
| Message-id |
<1271878193.2.0.986992462612.issue4256@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
I'll be happy to both fix things pointed by Steven and try some other approach, if that's required, but I would rather do it after a consesus is reached, so I don't have to do the same stuff several times (changing argparse tests requires some work - it's really awesome test suite).
What about optparse? Maybe there we can add this option without much thinking, by checking if help-options is used at the end of parsing? If not, we face the same problem as with argparse.
I don't really understand, why can't we just check if help-options is provided by the user and add our own, if it is not? Even if options are parsed several times (when doing some debugging I have seen my messages printed multiple times in help formatter), we should be able to inspect options in raw form and determine, whether --help-options is used. |
|