Update requirements.txt

[emiliom]

Update requirements.txt, based on Alex's guidance:

• Update my local env: conda/mamba env update -f environment.yml
• Regenerate requirements.txt via a pip freeze of the environment
• Update the repo

Doing this will minimize style differences between the deployed site and the netlify site previews.

See our 4/19 thread in the website Slack channel.

[abkfenris]

It might be worth making a 'locked environment' too, so that we have a known state that we can always pin to if needed. conda env export I believe.

[abkfenris]

Largely taken care of via #246

Of note, when trying to freeze a conda environment, the normal pip freeze doesn't work as it includes Conda package details. python -m pip list --format=freeze > requirements.txt is the trick.

[emiliom]

Woo-hoo! Thanks!

Largely taken care of via #246

Largely? Is what remains this?

It might be worth making a 'locked environment' too, so that we have a known state that we can always pin to if needed. conda env export I believe.

BTW, pinning to Python 3.8: not terrible, but yikes.

[abkfenris]

Ok, pretty much all taken care of, but I started pondering if we could remove the need for having different environments instead and then got distracted and never finished writing the issue...

[abkfenris]

Have you tried Pixi?

It really nicely helps manage a lock file for Conda and PyPI dependencies, and can track various tasks, so we could capture the docs serving and requirements freezing commands. I think we could automate requirements freezing reasonably with Github Actions (or at least checking), and getting Read the Docs to use it

[emiliom]

Have you tried Pixi?

I haven't, but my curiosity was piqued when you mentioned at the last SC meeting how it had matured.