pixi is a cross-platform, multi-language package manager and workflow tool built on the foundation of the conda ecosystem. It provides developers with an exceptional experience similar to popular package managers like cargo or npm, but for any language.
Developed with ❤️ at prefix.dev.
- Supports multiple languages including Python, C++, and R using Conda packages. You can find available packages on prefix.dev.
- Compatible with all major operating systems: Linux, Windows, macOS (including Apple Silicon).
- Always includes an up-to-date lock file.
- Provides a clean and simple Cargo-like command-line interface.
- Allows you to install tools per-project or system-wide.
- Entirely written in Rust and built on top of the rattler library.
- ⚡ Installation
- ⚙️ Examples
- ? Documentation
- ? Contributing
- ? Built using Pixi
- ? GitHub Action
Pixi is ready for production! We are working hard to keep file-format changes compatible with the previous versions so that you can rely on Pixi with peace of mind.
Some notable features we envision for upcoming releases are:
- Build and publish your project as a Conda package.
- Support for dependencies from source.
- More powerful "global installation" of packages towards a deterministic setup of global packages on multiple machines.
pixi can be installed on macOS, Linux, and Windows. The provided scripts will automatically download the latest version of pixi, extract it, and move the pixi binary to ~/.pixi/bin. If this directory does not exist, the script will create it.
To install Pixi on macOS and Linux, open a terminal and run the following command:
The script will also update your ~/.bashrc to include ~/.pixi/bin in your PATH, allowing you to invoke the pixi command from anywhere. You might need to restart your terminal or source your shell for the changes to take effect.
Starting with macOS Catalina zsh is the default login shell and interactive shell. Therefore, you might want to use zsh instead of bash in the install command:
The script will also update your ~/.zshrc to include ~/.pixi/bin in your PATH, allowing you to invoke the pixi command from anywhere.
To install Pixi on Windows, open a PowerShell terminal (you may need to run it as an administrator) and run the following command:
Changing the execution policy allows running a script from the internet. Check the script you would be running with:
The script will inform you once the installation is successful and add the ~/.pixi/bin directory to your PATH, which will allow you to run the pixi command from any location. Or with winget
To get autocompletion follow the instructions for your shell. Afterwards, restart the shell or source the shell config file.
Add the following to the end of ~/.bashrc:
Add the following to the end of ~/.zshrc:
Add the following to the end of Microsoft.PowerShell_profile.ps1. You can check the location of this file by querying the $PROFILE variable in PowerShell. Typically the path is ~DocumentsPowerShellMicrosoft.PowerShell_profile.ps1 or ~/.config/powershell/Microsoft.PowerShell_profile.ps1 on -Nix.
Add the following to the end of ~/.config/fish/config.fish:
Add the following to your Nushell config file (find it by running $nu.config-path in Nushell):
Add the following to the end of ~/.elvish/rc.elv:
You can install pixi from the extra repository using pacman:
pixi is available for Alpine Edge. It can be installed via apk after enabling the testing repository.
pixi is 100% written in Rust and therefore it can be installed, built and tested with cargo. To start using pixi from a source build run:
We don't publish to crates.io anymore, so you need to install it from the repository. The reason for this is that we depend on some unpublished crates which disallows us to publish to crates.io.
If you install pixi that way, it isn't necessarily the first in your PATH. The one installed by the installation script might take precedence. Therefore, we recommend running the following task instead for local development:
This way, a new binary called pixid will be available without any name conflicts with other Pixi installations on your system.
To uninstall, the Pixi binary should be removed. Delete pixi from the $PIXI_DIR which is default to ~/.pixi/bin/pixi
So on Linux its:
and on Windows:
After this command you can still use the tools you installed with pixi. To remove these as well just remove the whole ~/.pixi directory and remove the directory from your path.
The cli looks as follows:
Initialize a new workspace and navigate to the workspace directory
Add the dependencies you want to use
Run the installed package in its environment
Activate a shell in the environment
Check out https://pixi.sh/dev/first_workspace/ for a more detailed introduction to workspaces.
You can also globally install conda packages into their own environment. This behavior is similar to pipx or condax.
You can use Pixi in GitHub Actions to install dependencies and run commands. It supports automatic caching of your environments.
See the documentation for more details.
We would absolutely love for you to contribute to Pixi! Whether you want to start an issue, fix a bug you encountered, or suggest an improvement, every contribution is greatly appreciated.
If you're just getting started with our project or stepping into the Rust ecosystem for the first time, we've got your back! We recommend beginning with issues labeled as good first issue. These are carefully chosen tasks that provide a smooth entry point into contributing.These issues are typically more straightforward and are a great way to get familiar with the project.
Got questions or ideas, or just want to chat? Join our lively conversations on Discord. We're very active and would be happy to welcome you to our community. Join our discord server today!
To see what's being built with pixi check out the Community page.
Hoặc