./devel/py-argparse-manpage, Build manual page from pythons ArgumentParser object

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]

Branch: CURRENT, Version: 4.6, Package name: py312-argparse-manpage-4.6, Maintainer: pkgsrc-users

Avoid documenting your Python script arguments on two places! This
is typically done in an argparse.ArgumentParser help configuration
(help=, description=, etc.), and also in a manually crafted manual
page.

The good thing about an ArgumentParser objects is that it actually
provides a traversable "tree-like" structure, with all the necessary
info needed to automatically generate documentation, for example
in a groff typesetting system (manual pages). And this is where
this project can help.

Master sites:

Filesize: 57.299 KB

Version history: (Expand)

CVS history: (Expand)


   2024-11-11 08:29:31 by Thomas Klausner | Files touched by this commit (862) 
Log message:
py-*: remove unused tool dependency

py-setuptools includes the py-wheel functionality nowadays
   2024-06-07 13:09:24 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
py-argparse-manpage: updated to 4.6

4.6
Fix the build against Python 3.13
   2023-10-28 21:57:26 by Thomas Klausner | Files touched by this commit (516) | Package updated
Log message:
python/wheel.mk: simplify a lot, and switch to 'installer' for installation

This follows the recommended bootstrap method (flit_core, build, installer).

However, installer installs different files than pip, so update PLISTs
for all packages using wheel.mk and bump their PKGREVISIONs.
   2023-10-06 21:40:25 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
py-argparse-manpage: updated to 4.5

News in v4.5

* We newly provide `build_manpages.build_py` and `build_manpages.install`
  command classes that are re-usable from `pyproject.toml`.  No need to
  provide `setup.py` because of `argparse-manpage`.

News in v4.4

* The `prog=` specifier (in setup.py/setup.cfg/pyproject.toml) is now
  better handled so it doesn't conflict with ArgumentParser(prog=..).
  Fixes https://github.com/praiskup/argparse-manpage/issues/79
   2023-06-20 10:20:53 by Adam Ciarcinski | Files touched by this commit (2) 
Log message:
py-argparse-manpage: fix post-install
   2023-06-01 06:30:44 by Thomas Klausner | Files touched by this commit (5) 
Log message:
devel/py-argparse-manpage: import py-argparse-manpage-4.3

Avoid documenting your Python script arguments on two places! This
is typically done in an argparse.ArgumentParser help configuration
(help=, description=, etc.), and also in a manually crafted manual
page.

The good thing about an ArgumentParser objects is that it actually
provides a traversable "tree-like" structure, with all the necessary
info needed to automatically generate documentation, for example
in a groff typesetting system (manual pages). And this is where
this project can help.