Message291879
| 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.11:21:13 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1492600873.56.0.666819863658.issue14102@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Your example just prints a man page. It doesn't do anything useful besides this. I'm asking how argparse can do two incompatible things: provide a command-line interface for an end user and generate a man page in a build script. Do you mean that the programmer should create a separate script for generating a man page and copy a part of the code from the main program? This workflow should be documented, with examples. And it is not applicable for simple one-file scripts. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2017-04-19 11:21:13 | 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 11:21:13 | serhiy.storchaka | set | messageid: <1492600873.56.0.666819863658.issue14102@psf.upfronthosting.co.za> |
| 2017-04-19 11:21:13 | serhiy.storchaka | link | issue14102 messages |
| 2017-04-19 11:21:13 | serhiy.storchaka | create | |