Matthew Feickert matthewfeickert

`pixi` resolution order for composing features to make environments

$ pixi --version
pixi 0.30.0

For testing purposes, I'm trying to create lock files for an ecosystem of tools across multiple Python versions. To avoid having to repeat describing the dependencies, I'd like to use pixi's features to define the tools once in one feature (with lower bounds only as this would be part of nightly/weekly solves) and then have the Python version exist in a separate feature. The goal here is to be able to create environments quickly by composing features together like

	version: 6
	environments:
	default:
	channels:
	- url: https://conda.anaconda.org/conda-forge/
	packages:
	linux-64:
	- conda: https://conda.anaconda.org/conda-forge/linux-64/_libgcc_mutex-0.1-conda_forge.tar.bz2
	- conda: https://conda.anaconda.org/conda-forge/linux-64/_openmp_mutex-4.5-2_gnu.tar.bz2
	- conda: https://conda.anaconda.org/conda-forge/noarch/annotated-types-0.7.0-pyhd8ed1ab_1.conda

	FROM mambaorg/micromamba:1.5.9-bookworm-slim

	USER mambauser

	SHELL [ "/bin/bash", "-c" ]

	# Use C.UTF-8 locale to avoid issues with unicode encoding
	ENV LC_ALL=C.UTF-8
	ENV LANG=C.UTF-8

	# build products
	output/
	example
	# pixi environments
	.pixi
	*.egg-info

	# SCM syntax highlighting & preventing 3-way merges
	pixi.lock merge=binary linguist-language=YAML linguist-generated=true

	# SCM syntax highlighting
	pixi.lock linguist-language=YAML linguist-generated=true

	# GitHub syntax highlighting
	pixi.lock linguist-language=YAML linguist-generated=true

Matthew Feickert matthewfeickert

pixi resolution order for composing features to make environments

`pixi` resolution order for composing features to make environments