Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Improved epilog and description interpretation
- Loading branch information
Showing
7 changed files
with
321 additions
and
19 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,28 @@ | ||
v0.2.0 | ||
====== | ||
This release just adds some new interpretation features to extract the | ||
parser description and the epilog from the parsed function. They might | ||
changed how your parser looks drastically! | ||
|
||
Changed | ||
------- | ||
* The default formatter_class for the :class:`FuncArgParser` is now the | ||
:class:`argparse.RawHelpFormatter`, which makes sense since we expect that | ||
the documentations are already nicely formatted | ||
* When calling the :meth:`FuncArgParser.setup_args` method, we also look for | ||
the *Notes* and *References* sections which will be included in the epilog | ||
of the parser. If you want to disable this feature, just initialize the | ||
parser with:: | ||
|
||
parser = FuncArgParser(epilog_sections=[]) | ||
|
||
This feature might cause troubles when being used in sphinx documentations | ||
in conjunction with the sphinx-argparse_ package. For this, you can change | ||
the formatting of the heading with the :attr:`FuncArgParser.epilog_formatter` | ||
attribute | ||
|
||
.. _sphinx-argparse: http://sphinx-argparse.readthedocs.io/en/latest/ | ||
|
||
Added | ||
----- | ||
* Changelog |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.