joint pip & conda packages

[geoHeil]

Is it possible to combine pip and conda dependencies in the new build mode https://pixi.sh/latest/build/backends/ of pixi?

[ruben-arts]

I might be missing some detail in your question. But maybe the python tutorial could help you: https://pixi.sh/latest/build/python/

The idea is that the [package.{type}-dependencies] are conda packages and the pypi dependencies go into the pyproject.toml.

[geoHeil]

yes they do.

Lets assume the following example:

• we build a library
• it contains both pip and conda packages
• the default build backend - hatchling is used

[build-system] 

build-backend = "hatchling.build"

As a consumer (of the library) do I get a pip, a conda or a pixi package that I can include in my downstream package?

If I get a pip package -> how can the other conda dependencies be represented then?

[geoHeil]

This #1841 is related i.e. depending on the answer of the question - what would be published?

[baszalmstra]

Our long term vision is that pixi build backends can (optionally) output multiple artifact types. We currently focus on conda packages but we plan on adding support for other types down the line.

When a package contains both conda and pypi dependencies we’ll have to do a reverse mapping from pypi packages to conda and vice versa. We already have a pretty solid base for going from conda to pypi (used by pixi already) and we think we can also do the inverse based on the same data that we already have.

With current pixi-build we already have preliminary support for building pyproject projects (as well as feedstocks and cmake based projects) but without any mapping. We will extend this more in the coming year! Its gonna be quite awesome! 😎

I hope that answers your questions?