Add pixi config to pyproject.toml

[Armavica]

Description

Related Issue

• Closes #
• Related to #

Checklist

• Checked that the pre-commit linting/style checks pass
• Included tests that prove the fix is effective or that the new feature works
• Added necessary documentation (docstrings and/or example notebooks)
• If you are a pro: each commit corresponds to a relevant logical change

Type of change

• New feature / enhancement
• Bug fix
• Documentation
• Maintenance
• Other (please specify):

[tomicapretto]

Does this work when you don't have anything defined under tool.pixi.features? IIUC, this is using the different entries under project.optional-dependencies, right?

[Armavica]

Yes, that's correct!

[tomicapretto]

I think this will only support development on linux?

[Armavica]

I suppose, but I wouldn't be able to test it on any other platform so I am thinking that it is easier if people who want support on other platforms add it themselves

[tomicapretto]

Why this empty entry?

[Armavica]

pixi init created this entry but one could add tasks. Maybe testing, running mypy, building the docs, etc?

[tomicapretto]

I like Pixi a lot and I've been using it almost everywhere now. We use it for Bambi and Formulae. If you want to have a look, these are the pyproject.toml https://github.com/bambinos/bambi/blob/main/pyproject.toml https://github.com/bambinos/formulae/blob/master/pyproject.toml. They are quite similar.

In short, we use setuptools for building the package, and pixi for anything dev related. Dev specific dependencies, such as those needed for tests, do not go into [project.optional-dependencies] and cannot be installed by users doing pip install .[test]. I like that separation between things we build and export, and things we use for development purposes.

With that said, I can imagine not everybody uses pixi for developing PyMCPyTensor, so it may not be possible to separate things in the same way.

[maresb]

Am on vacation until January, but see #1542 and feedback

[maresb]

The environment will be quite large, so we should probably think hard about if/where/how we store the lockfiles.

[jessegrabowski]

I suggest we use a CI job to have pixi to generate a conda env file if we're going this way, to keep everything automatically synced. Alternatively we could delete the environment.yaml we have now, but I hope we don't go that way yet -- I'm not all aboard the pixi train.

[maresb]

In my PR I generate pixi.toml directly from environment.yml. I will be back in a few days and be able to give detailed feedback then.