types#
Definition of specific return types for use when defining a conda plugin hook.
Each type corresponds to the plugin hook for which it is used.
Classes#
Base class for all conda plugins. |
|
Return type to use when defining a conda subcommand plugin hook. |
|
Return type to use when defining a conda virtual package plugin hook. |
|
Return type to use when defining a conda solver plugin hook. |
|
Return type to use when defining a conda pre-command plugin hook. |
|
Return type to use when defining a conda post-command plugin hook. |
|
Class mixin to make all plugin implementations compatible, e.g. when they |
|
Base class that we require all plugin implementations to use to be compatible. |
|
Return type to use when the defining the conda auth handlers hook. |
|
Return type to use when defining conda health checks plugin hook. |
|
Return type to use when defining a conda pre-solve plugin hook. |
|
Return type to use when defining a conda post-solve plugin hook. |
|
Return type to use when defining a conda setting plugin hook. |
|
Helper class that provides a standard way to create an ABC using |
|
Helper class that provides a standard way to create an ABC using |
|
Base class for all reporter renderers. |
|
Return type to use when defining a conda reporter backend plugin hook. |
|
Define vendor specific headers to include HTTP requests |
|
Return type to use when defining a pre-transaction action hook. |
|
Return type to use when defining a post-transaction action hook. |
|
Define new loaders to expose non-conda packages in a given prefix |
|
EXPERIMENTAL |
|
EXPERIMENTAL |
|
EXPERIMENTAL |
Attributes#
- CondaPrefixDataLoaderCallable: TypeAlias#
- class CondaSubcommand#
Bases:
CondaPluginReturn type to use when defining a conda subcommand plugin hook.
For details on how this is used, see
conda_subcommands().- Parameters:
name -- Subcommand name (e.g.,
conda my-subcommand-name).summary -- Subcommand summary, will be shown in
conda --help.action -- Callable that will be run when the subcommand is invoked.
configure_parser -- Callable that will be run when the subcommand parser is initialized.
- action: collections.abc.Callable[[argparse.Namespace | tuple[str]], int | None]#
- configure_parser: collections.abc.Callable[[argparse.ArgumentParser], None] | None#
- class CondaVirtualPackage#
Bases:
CondaPluginReturn type to use when defining a conda virtual package plugin hook.
For details on how this is used, see
conda_virtual_packages().Note
The
versionandbuildparameters can be provided in two ways:Direct values: a string or
None(whereNonetranslates to0)Deferred callables: functions that return either a string,
None(translates to0), orNULL(indicates the virtual package should not be exported)
- Parameters:
name -- Virtual package name (e.g.,
my_custom_os).version -- Virtual package version (e.g.,
1.2.3).build -- Virtual package build string (e.g.,
x86_64).override_entity -- Can be set to either to "version" or "build", the corresponding value will be overridden if the environment variable
CONDA_OVERRIDE_<name>is set.empty_override -- Value to use for version or build if the override environment variable is set to an empty string. By default, this is
NULL.version_validation -- Optional version validation function to ensure that the override version follows a certain pattern.
- to_virtual_package() conda.models.records.PackageRecord | conda.auxlib._Null#
- class CondaSolver#
Bases:
CondaPluginReturn type to use when defining a conda solver plugin hook.
For details on how this is used, see
conda_solvers().- Parameters:
name -- Solver name (e.g.,
custom-solver).backend -- Type that will be instantiated as the solver backend.
- backend: type[conda.core.solve.Solver]#
- class CondaPreCommand#
Bases:
CondaPluginReturn type to use when defining a conda pre-command plugin hook.
For details on how this is used, see
conda_pre_commands().- Parameters:
name -- Pre-command name (e.g.,
custom_plugin_pre_commands).action -- Callable which contains the code to be run.
run_for -- Represents the command(s) this will be run on (e.g.
installorcreate).
- action: collections.abc.Callable[[str], None]#
- class CondaPostCommand#
Bases:
CondaPluginReturn type to use when defining a conda post-command plugin hook.
For details on how this is used, see
conda_post_commands().- Parameters:
name -- Post-command name (e.g.,
custom_plugin_post_commands).action -- Callable which contains the code to be run.
run_for -- Represents the command(s) this will be run on (e.g.
installorcreate).
- action: collections.abc.Callable[[str], None]#
- class ChannelNameMixin(channel_name: str, *args, **kwargs)#
Class mixin to make all plugin implementations compatible, e.g. when they use an existing (e.g. 3rd party) requests authentication handler.
Please use the concrete
ChannelAuthBasein case you're creating an own implementation.
- class ChannelAuthBase(channel_name: str, *args, **kwargs)#
Bases:
ChannelNameMixin,requests.auth.AuthBaseBase class that we require all plugin implementations to use to be compatible.
Authentication is tightly coupled with individual channels. Therefore, an additional
channel_nameproperty must be set on therequests.auth.AuthBasebased class.
- class CondaAuthHandler#
Bases:
CondaPluginReturn type to use when the defining the conda auth handlers hook.
- Parameters:
name -- Name (e.g.,
basic-auth). This name should be unique and only one may be registered at a time.handler -- Type that will be used as the authentication handler during network requests.
- handler: type[ChannelAuthBase]#
- class CondaHealthCheck#
Bases:
CondaPluginReturn type to use when defining conda health checks plugin hook.
- action: collections.abc.Callable[[str, bool], None]#
- class CondaPreSolve#
Bases:
CondaPluginReturn type to use when defining a conda pre-solve plugin hook.
For details on how this is used, see
conda_pre_solves().- Parameters:
name -- Pre-solve name (e.g.,
custom_plugin_pre_solve).action -- Callable which contains the code to be run.
- class CondaPostSolve#
Bases:
CondaPluginReturn type to use when defining a conda post-solve plugin hook.
For details on how this is used, see
conda_post_solves().- Parameters:
name -- Post-solve name (e.g.,
custom_plugin_post_solve).action -- Callable which contains the code to be run.
- action: collections.abc.Callable[[str, tuple[conda.models.records.PackageRecord, Ellipsis], tuple[conda.models.records.PackageRecord, Ellipsis]], None]#
- class CondaSetting#
Bases:
CondaPluginReturn type to use when defining a conda setting plugin hook.
For details on how this is used, see
conda_settings().- Parameters:
name -- name of the setting (e.g.,
config_param)description -- description of the setting that should be targeted towards users of the plugin
parameter -- Parameter instance containing the setting definition
aliases -- alternative names of the setting
- parameter: conda.common.configuration.Parameter#
- class ProgressBarBase(description: str, **kwargs)#
Bases:
abc.ABCHelper class that provides a standard way to create an ABC using inheritance.
- finish()#
- classmethod get_lock()#
- class SpinnerBase(message: str, fail_message: str = 'failed\n')#
Bases:
abc.ABCHelper class that provides a standard way to create an ABC using inheritance.
- abstract __enter__()#
- abstract __exit__(exc_type, exc_val, exc_tb)#
- class ReporterRendererBase#
Bases:
abc.ABCBase class for all reporter renderers.
- abstract detail_view(data: dict[str, str | int | bool], **kwargs) str#
Render the output in a "tabular" format.
- abstract envs_list(data: collections.abc.Iterable[str] | dict[str, dict[str, str | bool | None]], **kwargs) str#
Render a list of environments
- abstract progress_bar(description: str, **kwargs) ProgressBarBase#
Return a
ProgressBarBase~object to use as a progress bar
- classmethod progress_bar_context_manager() contextlib.AbstractContextManager#
Returns a null context by default but allows plugins to define their own if necessary
- abstract spinner(message, failed_message) SpinnerBase#
Return a
SpinnerBase~object to use as a spinner (i.e. loading dialog)
- class CondaReporterBackend#
Bases:
CondaPluginReturn type to use when defining a conda reporter backend plugin hook.
For details on how this is used, see:
conda_reporter_backends().- Parameters:
name -- name of the reporter backend (e.g.,
email_reporter) This is how the reporter backend with be references in configuration files.description -- short description of what the reporter handler does
renderer -- implementation of
ReporterRendererBasethat will be used as the reporter renderer
- renderer: type[ReporterRendererBase]#
- class CondaRequestHeader#
Bases:
CondaPluginDefine vendor specific headers to include HTTP requests
For details on how this is used, see
conda_request_headers()andconda_session_headers().- Parameters:
name -- name of the header used in the HTTP request
value -- value of the header used in the HTTP request
- class CondaPreTransactionAction#
Bases:
CondaPluginReturn type to use when defining a pre-transaction action hook.
For details on how this is used, see
conda_pre_transaction_actions().- Parameters:
name -- Pre transaction name (this is just a label)
action -- Action class which implements plugin behavior. See
Actionfor implementation details
- action: type[conda.core.path_actions.Action]#
- class CondaPostTransactionAction#
Bases:
CondaPluginReturn type to use when defining a post-transaction action hook.
For details on how this is used, see
conda_post_transaction_actions().- Parameters:
name -- Post transaction name (this is just a label)
action -- Action class which implements plugin behavior. See
Actionfor implementation details
- action: type[conda.core.path_actions.Action]#
- class CondaPrefixDataLoader#
Bases:
CondaPluginDefine new loaders to expose non-conda packages in a given prefix as
PrefixRecordobjects.- Parameters:
name -- name of the loader
loader -- a function that takes a prefix and a dictionary that maps package names to
PrefixRecordobjects. The newly loaded packages must be inserted in the passed dictionary accordingly, and also returned as a separate dictionary.
- loader: CondaPrefixDataLoaderCallable#
- class EnvironmentSpecBase#
Bases:
abc.ABCEXPERIMENTAL
Base class for all environment specifications.
Environment specs parse different types of environment definition files (environment.yml, requirements.txt, pyproject.toml, etc.) into a common Environment object model.
- abstract property env: conda.models.environment.Environment#
Express the provided environment file as a conda environment object.
- Returns Environment:
the conda environment represented by the file.
- class CondaEnvironmentSpecifier#
Bases:
CondaPluginEXPERIMENTAL
Return type to use when defining a conda env spec plugin hook.
For details on how this is used, see
conda_environment_specifiers().- Parameters:
name -- name of the spec (e.g.,
environment_yaml)environment_spec -- EnvironmentSpecBase subclass handler
- environment_spec: type[EnvironmentSpecBase]#
- class CondaEnvironmentExporter#
Bases:
CondaPluginEXPERIMENTAL
Return type to use when defining a conda environment exporter plugin hook supporting a single platform.
- Parameters:
name -- name of the exporter (e.g.,
environment-yaml)aliases -- user-friendly format aliases (e.g., ("yaml",))
default_filenames -- default filenames this exporter handles (e.g., ("environment.yml", "environment.yaml"))
export -- callable that exports an Environment to string format
- __post_init__()#