callables ¤

Module containing callables for many tools.

Call to developers!

If you are the author or maintainer of one of the tools we support (or more generally if you are the author/maintainer of a Python CLI/library), we kindly request that you add such a callable to your code base. Why?

Most of the time, all duty can do is hook into the CLI entrypoint for the lack of a better alternative. This is not ideal because we have to translate function arguments to CLI arguments, that are then parsed again and translated back to Python objects by the tool itself. This is not efficient.
It is not feasible for duty to maintain callables for different versions of these tools. Having the callables maintained in the tools themselves would make this support transparent.
We believe it simply provides a better user- and developer-experience. Clear separation of concerns: don't intertwine logic into the CLI parser. Easy to maintain, easy to test. The CLI parser just has to translate CLI args to their equivalent Python arguments.

Tips for writing such a library entry point:

Make it equivalent to the CLI entry point: every flag and option must have an equivalent parameter. Slight customizations can be made to support --flag / --no-flag with single parameters.
Use only built-in types: don't make users import and use objects from your API. For example, accept a list of strings, not a list of MyCustomClass instances.

Modules:

autoflake –

Callable for autoflake.
black –

Callable for Black.
blacken_docs –

Callable for blacken-docs.
coverage –

Callable for Coverage.py.
flake8 –

Callable for Flake8.
interrogate –

Callable for Interrogate.
isort –

Callable for isort.
mkdocs –

Callable for MkDocs.
mypy –

Callable for Mypy.
pytest –

Callable for pytest.
ruff –

Callable for Ruff.
safety –

Callable for Safety.
ssort –

Callable for ssort.