Message291883
| Author | zbysz |
|---|---|
| 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.12:35:40 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1492605340.78.0.302725453867.issue14102@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
If you can import the module that defines the parser, and get at the generated parser, this should be trivial to integrate with the build system. Something like: PYTHONPATH=. python3 -c 'import mymodule; p=mymodule.make_parser(); p.print_manpage(file="mymodule.1")' This operation could either be done automatically during build always, or it could just be done by the developers and the man page put under version control. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2017-04-19 12:35:40 | zbysz | set | recipients: + zbysz, rhettinger, bethard, jwilk, eric.araujo, dmalcolm, Aaron.Meurer, bignose, andialbrecht, bochecha, tshepang, paul.j3, sigi, Daniel.Walsh, serhiy.storchaka, Ingo.Fischer, adregner, josh.r, Oz.Tiram, acucci, matthewjohn, louielu |
| 2017-04-19 12:35:40 | zbysz | set | messageid: <1492605340.78.0.302725453867.issue14102@psf.upfronthosting.co.za> |
| 2017-04-19 12:35:40 | zbysz | link | issue14102 messages |
| 2017-04-19 12:35:40 | zbysz | create | |