Making a Pixi project#
Pixi's biggest strength is its ability to create reproducible powerful and flexible projects. Let's go over the common steps to create a Pixi project.
Creating a Pixi project#
To create a new Pixi project, you can use the pixi init
command:
This command creates a new directory called my_project
with the following structure:
The pixi.toml
file is the manifest of your Pixi project.
It contains all the information about your project, such as its channels, platforms, dependencies, tasks, and more.
The one created by pixi init
is a minimal manifest that looks like this:
[workspace]
authors = ["Jane Doe <jane.doe@example.com>"]
channels = ["conda-forge"]
name = "my_project"
platforms = ["osx-arm64"]
version = "0.1.0"
[tasks]
[dependencies]
Do you want autocompletion of the manifest file?
As pixi.toml
has a JSON schema, it is possible to use IDE’s like VSCode to edit the field with autocompletion.
Install the Even Better TOML VSCode extension to get the best experience.
Or use the integrated schema support in PyCharm.
Managing dependencies#
After creating the project, you can start adding dependencies to the project.
Pixi uses the pixi add
command to add dependencies to the project.
This command will , by default, add the conda dependency to the pixi.toml
, solve the dependencies, write the lockfile and install the package in the environment.
For example, lets add numpy
and pytest
to the project.
You can also specify the version of the dependency you want to add.
PyPI dependencies#
Pixi normally uses conda
packages for dependencies, but you can also add dependencies from PyPI.
Pixi will make sure it doesn't try to install the same package from both sources, and avoid conflicts between them.
If you want to add them to your project you can do that with the --pypi
flag:
requests
package from PyPI to the project:
Lockfile#
Pixi will always create a lockfile when the dependencies are solved. This file will contain all the exact version of the packages and their dependencies. Resulting in a reproducible environment, that you can share with others or use for testing and deployment.
The lockfile is called pixi.lock
and it is created in the root of the project.
It contains all the information about the dependencies, such as their versions, channels, platforms, and more.
version: 6
environments:
default:
channels:
- url: https://prefix.dev/conda-forge/
indexes:
- https://pypi.org/simple
packages:
osx-arm64:
- conda: https://prefix.dev/conda-forge/osx-arm64/bzip2-1.0.8-h99b78c6_7.conda
- pypi: ...
packages:
- conda: https://prefix.dev/conda-forge/osx-arm64/bzip2-1.0.8-h99b78c6_7.conda
sha256: adfa71f158cbd872a36394c56c3568e6034aa55c623634b37a4836bd036e6b91
md5: fc6948412dbbbe9a4c9ddbbcfe0a79ab
depends:
- __osx >=11.0
license: bzip2-1.0.6
license_family: BSD
size: 122909
timestamp: 1720974522888
- pypi: ...
Managing tasks#
Pixi has a built-in cross-platform task runner that allows you to define tasks in the manifest.
This is a great way to share tasks with others and to ensure that the same tasks are run in the same environment.
The tasks are defined in the pixi.toml
file under the [tasks]
section.
You can add one to your project by running the pixi task add
command.
pixi.toml
file:
You can then run the task using the pixi run
command:
This will execute the command echo Hello, World!
in the environment.
Do you want use more powerful features?
Tasks can be much more powerful for example:
[tasks.name-of-powerful-task]
cmd = "echo This task can do much more! Like have {{ arguments }} and {{ "minijinja" | capitalize }} templates."
# List of tasks that must be run before this one.
depends-on = ["other-task"]
# Working directory relative to the root of the project
cwd = "current/working/directory"
# Define required arguments for the task
args = [{ arg = "arguments", default = "default arguments" }]
# Only run if the input files have changed
input = ["src"]
# Only run if the output files are missing
output = ["output.txt"]
# Set environment variables for the task
env = { MY_ENV_VAR = "value" }
Environments#
Pixi always creates a virtual environment for your project.
These environments are located in the .pixi/envs
directory in the root of your project.
Using these environments is as simple as running the pixi run
or pixi shell
command.
These commands will automatically activate the environment and run the command in it.