pixi shell

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

Note

Never put the pixi shell command inside one of your shell's startup files (.profile, .bashrc and the likes): the command starts a new shell without special arguments so the new shell will again execute your startup files, which in turn will again run pixi shell and so on, recursively until failure.

Use shell-hook instead if you want to activate a pixi environment when your shell starts.

Usage

pixi shell [OPTIONS]

Options

• --environment (-e) <ENVIRONMENT>

  The environment to activate in the shell

Config Options

• --auth-file <AUTH_FILE>

  Path to the file containing the authentication token

• --concurrent-downloads <CONCURRENT_DOWNLOADS>

  Max concurrent network requests, default is 50

• --concurrent-solves <CONCURRENT_SOLVES>

  Max concurrent solves, default is the number of CPUs

• --pinning-strategy <PINNING_STRATEGY>

  Set pinning strategy
  options: semver, minor, major, latest-up, exact-version, no-pin

• --pypi-keyring-provider <PYPI_KEYRING_PROVIDER>

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

• --run-post-link-scripts

  Run post-link scripts (insecure)

• --tls-no-verify

  Do not verify the TLS certificate of the server

• --tls-root-certs <TLS_ROOT_CERTS>

  Which TLS root certificates to use: 'webpki' (bundled Mozilla roots), 'native' (system store), or 'all' (both)
  env: PIXI_TLS_ROOT_CERTS

• --use-environment-activation-cache

  Use environment activation cache (experimental)

• --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-completions

  Do not source the autocompletion scripts from the environment

Update Options

• --no-install

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

• --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

• --as-is

  Shorthand for the combination of --no-install and --frozen

Global Options

• --manifest-path (-m) <MANIFEST_PATH>

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

• --workspace (-w) <WORKSPACE>

  Name of the workspace

Examples

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