I think this should be something that is not included in argparse itself. I can imagine a scenario in which the manpage is accessible through `./python foo.py --manpage` but the manpage is not installed systemwide. This will be very confusing for users. Also, as Serhiy comments, argparse provides functionality that at this point is relevant for the enduser of the application. Generating a man page in a build script sounds like something that should be on its own or as a help function of the build system. The only thing argparse could do (maybe) is trying to read an already installed manpage and use that, but I still think that is not a good idea because it can generate conflicts and similar if multiple versions are installed or if the help of the package deviates from the manpage.