Message291866
| Author | serhiy.storchaka |
|---|---|
| Recipients | Aaron.Meurer, Daniel.Walsh, Ingo.Fischer, Oz.Tiram, acucci, adregner, andialbrecht, bethard, bignose, bochecha, dmalcolm, eric.araujo, josh.r, jwilk, louielu, matthewjohn, paul.j3, rhettinger, serhiy.storchaka, sigi, tshepang, zbysz |
| Date | 2017-04-19.08:02:19 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1492588939.58.0.424506507072.issue14102@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
How to use this feature? argparse is executed every time when the end user runs the program. But generating a man page is the action that should be executed at develop or build stage. The end user gets a generated man page, he doesn't need the option to generate a man page on a fly. The developer needs the ability to generate a man page rather than running the program for its main purpose. What should be the structure of the program that uses argparse for parsing arguments and for generating a man page? How generating a man page should be invoked? |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2017-04-19 08:02:19 | serhiy.storchaka | set | recipients: + serhiy.storchaka, rhettinger, bethard, jwilk, eric.araujo, zbysz, dmalcolm, Aaron.Meurer, bignose, andialbrecht, bochecha, tshepang, paul.j3, sigi, Daniel.Walsh, Ingo.Fischer, adregner, josh.r, Oz.Tiram, acucci, matthewjohn, louielu |
| 2017-04-19 08:02:19 | serhiy.storchaka | set | messageid: <1492588939.58.0.424506507072.issue14102@psf.upfronthosting.co.za> |
| 2017-04-19 08:02:19 | serhiy.storchaka | link | issue14102 messages |
| 2017-04-19 08:02:19 | serhiy.storchaka | create | |