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 bignose
Recipients Aaron.Meurer, Daniel.Walsh, Ingo.Fischer, Oz.Tiram, adregner, andialbrecht, bethard, bignose, bochecha, dmalcolm, eric.araujo, josh.r, jwilk, rhettinger, sigi, tshepang
Date 2016-03-08.19:45:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1457466339.75.0.539674435761.issue14102@psf.upfronthosting.co.za>
In-reply-to
Content
Oz Tiram wrote:

> I doubt if the correct place for formatting a man page should be in argparse.py itself. My solution is an extension of Andial's brecht solution

Thank you for that, Oz.

I see an easy seam to refactor this work into separate concerns.

The formatting of a man page from the parser for the command, can be coupled to the ‘argparse’ module since it is dependent only on an ArgumentParser plus some extra properties for populating the man page.

The building of one man page should not, IMO, be so tightly coupled to a Python distribution. There may be several different commands installed by one distribution. Each man page's fields should mostly come from the parser for the command, not from the distribution metadata. Instead, the build process should be told which parser to use for generating each of the man pages.

I propose to work on Oz's module and produce a man page formatter for exactly one ArgumentParser, as an enhancement for ‘argparse’.
History
Date User Action Args
2016-03-08 19:45:39bignosesetrecipients: + bignose, rhettinger, bethard, jwilk, eric.araujo, dmalcolm, Aaron.Meurer, andialbrecht, bochecha, tshepang, sigi, Daniel.Walsh, Ingo.Fischer, adregner, josh.r, Oz.Tiram
2016-03-08 19:45:39bignosesetmessageid: <1457466339.75.0.539674435761.issue14102@psf.upfronthosting.co.za>
2016-03-08 19:45:39bignoselinkissue14102 messages
2016-03-08 19:45:39bignosecreate