The following API documentation was automatically generated from the source code of humanfriendly |release|:

The humanfriendly package started out as a single :mod:`humanfriendly` module. Eventually this module grew to a size that necessitated splitting up the code into multiple modules (see e.g. :mod:`~humanfriendly.tables`, :mod:`~humanfriendly.terminal`, :mod:`~humanfriendly.text` and :mod:`~humanfriendly.usage`). Most of the functionality that remains in the :mod:`humanfriendly` module will eventually be moved to submodules as well (as time permits and a logical subdivision of functionality presents itself to me).

While moving functionality around like this my goal is to always preserve backwards compatibility. For example if a function is moved to a submodule an import of that function is added in the main module so that backwards compatibility with previously written import statements is preserved.

If backwards compatibility of documented functionality has to be broken then the major version number will be bumped. So if you're using the humanfriendly package in your project, make sure to at least pin the major version number in order to avoid unexpected surprises.

.. automodule:: humanfriendly
   :members:

.. automodule:: humanfriendly.case
   :members:

.. automodule:: humanfriendly.cli
   :members:

.. automodule:: humanfriendly.compat
   :members: coerce_string, is_string, is_unicode, on_macos, on_windows

.. automodule:: humanfriendly.decorators
   :members:

.. automodule:: humanfriendly.deprecation
   :members:

.. automodule:: humanfriendly.prompts
   :members:

.. automodule:: humanfriendly.sphinx
   :members:

.. automodule:: humanfriendly.tables
   :members:

.. automodule:: humanfriendly.terminal
   :members:

.. automodule:: humanfriendly.terminal.html
   :members:

.. automodule:: humanfriendly.terminal.spinners
   :members:

.. automodule:: humanfriendly.testing
   :members:

.. automodule:: humanfriendly.text
   :members:

.. automodule:: humanfriendly.usage
   :members: