Move to Pixi

[jaimergp]

Comes from #release > 0.7.0 @ 💬

[jaimergp]

I started doing this (see folded pixi.toml), but our current workflow patches environments with editable installs of napari/napari, which is not well supported in Pixi. Forcing it to behave like this is going to be not very maintainable, so for now I'm going to put this aside and focus on the documentation #287.

pixi.toml

[workspace]
authors = ["jaimergp <jaimergp@users.noreply.github.com>"]
channels = ["conda-forge"]
name = "napari-packaging"
platforms = ["linux-64", "linux-aarch64", "osx-64", "osx-arm64", "win-64"]
version = "0.1.0"

[feature.package.tasks]
build-package = "rattler-build "

[feature.package.dependencies]
rattler-build = "*"
conda-smithy = ">=3.37.0"
python = "3.10.*"
pip = "*"
tomlkit = "*"
"ruamel.yaml" = "*"
anaconda-client = "*"
setuptools = "*"
shyaml = "*"

[feature.installer.tasks]
build-installer = "rattler"

[feature.installer.dependencies]
python = "*"
pip = "*"
constructor  = ">=3.11.0"
conda-build  = ">=3.28"
"ruamel.yaml" = "*"
conda-standalone  = ">=24.7.1"
conda = ">=24.7.1"
# only needed to import napari and get the path to the logo.png file = "*"
lazy_loader  = ">=0.2"
numpy  = ">=1.22.2"

[environments]
packages = ["package"]
installers = ["installer"]

[Czaki]

Moving to pixi will allow better management of dependencies in the bundle (no longer required dependencies will be uninstalled after remove plugin)?

[jaimergp]

This doesn't affect the built installers. Pixi won't be shipped there. This issue is about having this repo instrumented with pixi so we can do things like:

$ pixi run build-packages
$ pixi run build-installers

Instead of the multistep dev workflow documented at #290 (which needs review, btw)