Unified package dependency management for Python and Conda build backends?

[millsks]

I would like to be able to build both Python files (wheel,sdist) and Conda packages. How can I use Pixi to store all package dependencies in one place rather than across multiple sources depe ding on the package being built.

For example, Conda packages built with rattler-build will use the recipe.yaml, and the Python project will use pyproject.toml. Does an approach exist where I can configure pixi dependencies and environments to combine both the recipe.yaml and dependency section from pyproject.toml into a single configuration that both build backend can read from?

[lucascolley]

you can do this in one manifest, but right now it requires tracking workspace dependencies and package dependencies separately.

For example, https://github.com/lucascolley/pixi-dev-scipystack/blob/28c00dde18c2d9391e69ffcabfb6e003b16f2271/scipy/pixi.toml shows a setup for building a conda package from SciPy with pixi-build-python, as well as a task to build a wheel in the workspace.

Right now pixi-build is focussed on conda packages, but there may be scope to also build other types of packages in the future.

[millsks]

Thanks, Lucas. Do you know if the Pixi build backends will be available on conda-forge this year? Is there a roadmap for Pixi that we can review and follow along?

We are currently working towards getting Pixi approved within the Enterprise, which will include accessing the channels on prefix.dev, but until then, we only have access to conda-forge through remote proxies configured to pull from conda.anaconda.org/conda-forge.

Right now, I am cloning the build backend repo and building them locally for testing purposes.

[lucascolley]

https://prefix.dev/channels/conda-forge/packages/pixi-build-python :)

[lucascolley]

I don't think we have a public grand roadmap for Pixi, but feel free to enquire about the priority of specific features

[millsks]

Thanks! And will do.

[millsks]

Thanks again @lucascolley. This should get me going. I opened up a separate discussion to propose a new build backend that could possibly handle doing this in the future and to avoid tracking workspace and package dependencies separately.