Coming from pipx#
If you already use pipx, this guide maps each pipx command to its conda-global equivalent.
Command mapping#
pipx |
conda-global |
Notes |
|---|---|---|
|
|
Works with any conda package, not just Python |
|
|
|
|
|
|
|
|
Skips pinned tools |
|
|
Also supports |
|
|
Creates a temp env, cleans up after |
|
|
|
|
|
|
|
|
Same concept |
|
|
Prevents upgrades |
|
|
|
— |
|
Expose additional binaries |
— |
|
Remove an exposed binary |
— |
|
Reconcile filesystem with manifest |
— |
|
Show dependency tree |
— |
|
Open manifest in editor |
Key differences#
- Package ecosystem
pipx installs Python packages from PyPI. conda-global installs packages from conda channels — Python, R, Rust, C/C++, and more.
- Isolation mechanism
pipx creates virtualenvs. conda-global creates full conda environments, so compiled dependencies (OpenSSL, CUDA, etc.) are properly isolated too.
- Launcher
pipx uses Python wrapper scripts. conda-global uses a compiled Rust trampoline that calls
execvpdirectly — no interpreter startup.- Manifest
pipx has no manifest file. conda-global writes
global.toml, which can be shared across machines and synced withconda global sync.- Environment naming
pipx names environments after the package. conda-global defaults to the package name but lets you override it with
-e:conda global install gh -e github-cli
Migration workflow#
List your pipx tools:
pipx list --short
Install each one with conda-global:
conda global install ruff conda global install black conda global install gh
Verify they work:
ruff --version black --version gh --version
Once satisfied, remove the pipx versions:
pipx uninstall ruff pipx uninstall black pipx uninstall gh
Tip
Many popular Python tools are available on conda-forge with the same name as on PyPI. If a package isn’t available, check anaconda.org or request it on conda-forge/staged-recipes.