Skip to content

Conversation

@tristan-f-r
Copy link
Collaborator

@tristan-f-r tristan-f-r commented Aug 28, 2025

Pixi recently resolved an issue which was blocking my previous attempt at using pixi (one that, while it seemed to work locally, hangs on GitHub CI).

Other than installing pixi, one just needs to do pixi shell instead of conda init ... and conda activate spras. We also do not need to do pip install . anymore, as pixi automatically installs our local spras dependency - I'm not sure how well this pairs with #332.


I believe the actual infrastructure changes are otherwise minor and fine: the real review comes into making sure we're good on documenting pixi usage.

@tristan-f-r tristan-f-r added the infrastructure misc. changes made to SPRAS itself label Aug 28, 2025
@tristan-f-r tristan-f-r changed the title Pixi 2 chore: pixi Aug 28, 2025
@read-the-docs-community
Copy link

read-the-docs-community bot commented Aug 28, 2025

Documentation build overview

📚 spras | 🛠️ Build #30059945 | 📁 Comparing 68e3b01 against latest (615e6fb)


🔍 Preview build

Show files changed (6 files in total): 📝 6 modified | ➕ 0 added | ➖ 0 deleted
File Status
htcondor.html 📝 modified
install.html 📝 modified
usage.html 📝 modified
contributing/index.html 📝 modified
tutorial/beginner.html 📝 modified
tutorial/introduction.html 📝 modified

@tristan-f-r tristan-f-r mentioned this pull request Sep 6, 2025
@agitter
Copy link
Collaborator

agitter commented Oct 3, 2025

I need to take some time to use pixi locally before I can review this. I haven't been able to do that yet.

@github-actions github-actions bot added the merge-conflict This PR has merge conflicts. label Oct 13, 2025
@github-actions github-actions bot removed the merge-conflict This PR has merge conflicts. label Oct 14, 2025
@tristan-f-r
Copy link
Collaborator Author

There's also a really good chance that this can close #373.

@github-actions github-actions bot added the merge-conflict This PR has merge conflicts. label Oct 17, 2025
@github-actions github-actions bot removed the merge-conflict This PR has merge conflicts. label Oct 17, 2025
@agitter
Copy link
Collaborator

agitter commented Oct 19, 2025

There are two potentially separate decisions here:

  1. What should we use to run our CI testing
  2. What should we recommend users do to install and run SPRAS

For 1), I don't have strong opinions. Anything that is fast, reliable, maintained, and easy for us to maintain works. If pixi improves on conda in those or other respects I'd like to know how.

For 2), we should give more though to who are users are and what they are accustomed to. Installing software with conda is fairly common for computational and biological users. Should that remain the primary/secondary option and pixi the secondary/primary? Supporting two installation pathways leads to a higher maintenance burden, which I don't like.

@tristan-f-r
Copy link
Collaborator Author

For 2, we can avoid the 'installing conda/pixi' step entirely hopefully with #332, so I'm not too concerned about it. For the time being, encouraging users to use pixi seems fine.

@tristan-f-r
Copy link
Collaborator Author

As for 1, Snakemake itself uses Pixi for CI (and for development!), and unlike Conda, Pixi seems to not have flaky CI. I've had to restart CI in SPRAS for the flaky PCA test, and for flaky conda installations.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

infrastructure misc. changes made to SPRAS itself

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants