yIf U d Z ddlmZ ddlmZmZmZ ddlZdZ ededef Z ej
e Z d e d
< d Z
dS ) a
tox uses `pluggy `_ to customize the default behavior. It provides an
extension mechanism for plugin management by calling hooks.
Pluggy discovers a plugin by looking up for entry-points named ``tox``, for example in a pyproject.toml:
.. code-block:: toml
[project.entry-points.tox]
your_plugin = "your_plugin.hooks"
Therefore, to start using a plugin, you solely need to install it in the same environment tox is running in and it will
be discovered via the defined entry-point (in the example above, tox will load ``your_plugin.hooks``).
A plugin is created by implementing extension points in the form of hooks. For example the following code snippet would
define a new ``--magic`` command line interface flag the user can specify:
.. code-block:: python
from tox.config.cli.parser import ToxParser
from tox.plugin import impl
@impl
def tox_add_option(parser: ToxParser) -> None:
parser.add_argument("--magic", action="store_true", help="magical flag")
You can define such hooks either in a package installed alongside tox or within a ``toxfile.py`` found alongside your
tox configuration file (root of your project).
) annotations)AnyCallableTypeVarNtox_F.)boundzCallable[[_F], _F]impl)NAMEr
)__doc__
__future__r typingr r r pluggyr r HookimplMarkerr
__annotations____all__ G/var/www/piapp/venv/lib/python3.11/site-packages/tox/plugin/__init__.pyr s > # " " " " " ) ) ) ) ) ) ) ) ) )
WT#s(+,,,06066 6 6 6 6 r