2.2 KiB
Environment plugins
See the documentation for environment configuration.
Known third-party
- hatch-conda - environments backed by Conda/Mamba
- hatch-containers - environments run inside containers
- hatch-pip-deepfreeze - virtual environments with dependency locking by pip-deepfreeze
Life cycle
Whenever an environment is used, the following logic is performed:
::: hatch.cli.application.Application.prepare_environment options: show_root_heading: false show_root_toc_entry: false
Build environments
All environment types should offer support for a special sub-environment in which projects can be built. This environment is used in the following scenarios:
- the
buildcommand - commands that read dependencies, like
dep hash, if any project dependencies are set dynamically
::: hatch.env.plugin.interface.EnvironmentInterface options: members: - PLUGIN_NAME - app - root - name - data_directory - config - platform - environment_dependencies - dependencies - env_vars - env_include - env_exclude - platforms - skip_install - dev_mode - description - activate - deactivate - find - create - remove - exists - install_project - install_project_dev_mode - dependencies_in_sync - sync_dependencies - build_environment - build_environment_exists - get_build_process - construct_build_command - command_context - enter_shell - run_shell_command - resolve_commands - get_env_vars - apply_features - construct_pip_install_command - join_command_args - check_compatibility - get_option_types - get_env_var_option - get_context