Can you have both pixi.toml (for system deps and non Python requirements) and pyproject.toml (for Python package requirements) in a project

[Robinlovelace]

Basically as the title suggests. Context: working with @wangzhao0217 and others on teaching materials that will use R and Python. If the Python deps can be in a pyproject.toml file that is called from the higher level pixi.toml file that could make the project more modular and useful for people who don't care about installing R. Is that possible though?

Here's our repo for reference (see PR where we're managing Python deps in CI, would be good if a single pixi.toml could handle deps in one place): itsleeds/TDStests#22

[ruben-arts]

It's not entirely clear to me what you are requesting, but you can have both yes.

You can also just use a pyproject.toml and create a seperate environment that doesn't use the "default" parts of the pyproject.toml

You can also let pixi handle your ci setup: https://github.com/marketplace/actions/setup-pixi which can then do the setup of a ci environment with exactly everything you want. instead of these multiple setup-xxx's which allowes you to test the CI environment locally.

[Robinlovelace]

Just to be clear: if you do

pixi install 

in a project with both pixi.toml and pyproject.toml config files, will pixi

a) Install the system deps definied in the former

b) then install the Python pkgs defined in the latter

?

Is there a way to do something like

[python-pkgs]
  [pyproject = "path-to-pyproject.toml"]

Hope this makes sense, apologies if I've asked something non-sensical, learning as I go.

[ruben-arts]

Ah you might want to checkout the [pypi-dependencies]: https://pixi.sh/latest/reference/project_configuration/#path

You can do in a pixi.toml:

[pypi-dependencies]
# This will look for a package called `minimal-project` in the folder `minimal-project`.
# If it is a Python package it will find a way to install it.
minimal-project = { path = "./minimal-project", editable = true}

This doesn't import packages it just installs a python package for you that can be path based and editable. Which includes installing the dependencies.

---

If you are looking to simply import the pyproject.toml, and you don't have an actual Python package. I would motivate you to use the pyproject.toml directly or skip it completely.

For example this is a pyproject.toml which can be used by pip and pixi:

[project]
name = "pixi-py"
# Setup your python here
requires-python = ">= 3.11"
# Whatever pypi dependencies you need.
dependencies = ["pypi-packages"]

[tool.pixi.project]
channels = ["conda-forge"]
platforms = ["osx-arm64"]

[tool.pixi.dependencies]
jupyter = "*"
# etc..

Which is equivalent to this pixi.toml:

[project]
name = "pixi-py"
channels = ["conda-forge"]
platforms = ["osx-arm64"]

# Put the pypi dependencies here instead of `[project.dependencies]`
[pypi-dependencies]
pypi-packages = "*"
# etc...

[dependencies]
python = ">=3.11"
jupyter = "*"
# etc...

[Robinlovelace]

Sounds good and yes I think we'll go with either or. We have currently gone with the following pixi.toml:

[project]
channels = ["conda-forge"]
description = "Add a short description here"
name = "TDStests"
platforms = ["win-64"]
version = "0.1.0"

[tasks]

[dependencies]
jupyter = "*"
jupyter-cache = "*"
geopandas = "*"
matplotlib = "*"
shapely = "*"
seaborn = "*"
quarto = "*"
r-base = "*"
r-irkernel = "*"
r-tidyverse = "*"
r-sf = "*"
r-quarto = "*"
r-nycflights13 = "*"
r-remotes = "*"
r-DT = "*"
r-reticulate = "*"
r-spData = "*"
r-pak = "*"

Follow-up question: is there a way to state the non-Python system deps in an equivalent pyproject.toml?

I'm thinking some of the things in there, like R, are quite pixi-specific so we should stick with the pixi.toml file.

What I dislike about that solution is that it reduces accessibility for people who have Python but not pixi installed, if you see what I mean?

Any further thoughts/guidance welcome.