docformatter
The Python docformatter tool (https://github.com/myint/docformatter).
Backend: pants.backend.python.lint.docformatter
Config section: [docformatter]
Basic options
args
--docformatter-args="[<shell_str>, <shell_str>, ...]"PANTS_DOCFORMATTER_ARGS[docformatter]
args = [
<shell_str>,
<shell_str>,
...,
]
[]Arguments to pass directly to docformatter, e.g. --docformatter-args='--wrap-summaries=100 --pre-summary-newline'.
export
--[no-]docformatter-exportPANTS_DOCFORMATTER_EXPORT[docformatter]
export = <bool>
TrueIf true, export a virtual environment with docformatter when running /home/josh/work/scie-pants/dist/pants export.
This can be useful, for example, with IDE integrations to point your editor to the tool's binary.
skip
--[no-]docformatter-skipPANTS_DOCFORMATTER_SKIP[docformatter]
skip = <bool>
FalseDon't use docformatter when running /home/josh/work/scie-pants/dist/pants fmt and /home/josh/work/scie-pants/dist/pants lint.
Advanced options
console_script
--docformatter-console-script=<str>PANTS_DOCFORMATTER_CONSOLE_SCRIPT[docformatter]
console_script = <str>
docformatterThe console script for the tool. Using this option is generally preferable to (and mutually exclusive with) specifying an --entry-point since console script names have a higher expectation of staying stable across releases of the tool. Usually, you will not want to change this from the default.
entry_point
--docformatter-entry-point=<str>PANTS_DOCFORMATTER_ENTRY_POINT[docformatter]
entry_point = <str>
NoneThe entry point for the tool. Generally you only want to use this option if the tool does not offer a --console-script (which this option is mutually exclusive with). Usually, you will not want to change this from the default.
extra_requirements
--docformatter-extra-requirements="['<str>', '<str>', ...]"PANTS_DOCFORMATTER_EXTRA_REQUIREMENTS[docformatter]
extra_requirements = [
'<str>',
'<str>',
...,
]
[]Any additional requirement strings to use with the tool. This is useful if the tool allows you to install plugins or if you need to constrain a dependency to a certain version.
interpreter_constraints
--docformatter-interpreter-constraints="['<str>', '<str>', ...]"PANTS_DOCFORMATTER_INTERPRETER_CONSTRAINTS[docformatter]
interpreter_constraints = [
'<str>',
'<str>',
...,
]
[ "CPython>=3.7,<4" ]
Python interpreter constraints for this tool.
lockfile
--docformatter-lockfile=<str>PANTS_DOCFORMATTER_LOCKFILE[docformatter]
lockfile = <str>
<default>Path to a lockfile used for installing the tool.
Set to the string <default> to use a lockfile provided by Pants, so long as you have not changed the --version and --extra-requirements options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by [python].invalid_lockfile_behavior). See https://github.com/pantsbuild/pants/blob/release_2.13.1/src/python/pants/backend/python/lint/docformatter/docformatter.lock for the default lockfile contents.
Set to the string <none> to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.
To use a custom lockfile, set this option to a file path relative to the build root, then run /home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=docformatter.
As explained at https://www.pantsbuild.org/v2.13/docs/python-third-party-dependencies, lockfile generation via generate-lockfiles does not always work and you may want to manually generate the lockfile. You will want to set [python].invalid_lockfile_behavior = 'ignore' so that Pants does not complain about missing lockfile headers.
version
--docformatter-version=<str>PANTS_DOCFORMATTER_VERSION[docformatter]
version = <str>
docformatter>=1.4,<1.5Requirement string for the tool.
Deprecated options
None
Related subsystems
None