pixi shell

About

Start a shell in a pixi environment, run exit to leave the shell

Usage

pixi shell [OPTIONS]

Config Options

• --tls-no-verify

  Do not verify the TLS certificate of the server

• --auth-file <AUTH_FILE>

  Path to the file containing the authentication token

• --pypi-keyring-provider <PYPI_KEYRING_PROVIDER>

  Specifies whether to use the keyring to look up credentials for PyPI
  options: disabled, subprocess

• --concurrent-solves <CONCURRENT_SOLVES>

  Max concurrent solves, default is the number of CPUs

• --concurrent-downloads <CONCURRENT_DOWNLOADS>

  Max concurrent network requests, default is 50

• --change-ps1 <CHANGE_PS1>

  Do not change the PS1 variable when starting a prompt
  options: true, false

• --force-activate

  Do not use the environment activation cache. (default: true except in experimental mode)

• --no-completion <NO_COMPLETION>

  Do not source the autocompletion scripts from the environment
  options: true, false

Update Options

• --no-install

  Don't modify the environment, only modify the lock-file

• --revalidate

  Run the complete environment validation. This will reinstall a broken environment

• --no-lockfile-update

  Don't update lockfile, implies the no-install as well

• --frozen

  Install the environment as defined in the lockfile, doesn't update lockfile if it isn't up-to-date with the manifest file
  env: PIXI_FROZEN

• --locked

  Check if lockfile is up-to-date before installing the environment, aborts when lockfile isn't up-to-date with the manifest file
  env: PIXI_LOCKED

• --environment (-e) <ENVIRONMENT>

  The environment to activate in the shell

Global Options

• --manifest-path <MANIFEST_PATH>

  The path to pixi.toml, pyproject.toml, or the workspace directory

Examples

pixi shell
pixi shell --manifest-path ~/myworkspace/pixi.toml
pixi shell --frozen
pixi shell --locked
pixi shell --environment cuda
exit