feat: prioritize mamba over conda, allow passing environment target name to installation

[FabianHofmann]

Closes # (if applicable).

Changes proposed in this Pull Request

Checklist

• I tested my contribution locally and it works as intended.
• Code and workflow changes are sufficiently documented.
• Changed dependencies are added to envs/environment.yaml.
• Changes in configuration options are added in config/config.default.yaml.
• Changes in configuration options are documented in doc/configtables/*.csv.
• Sources of newly added data are documented in doc/data_sources.rst.
• A release note doc/release_notes.rst is added.

[github-actions]

Validator Report

I am the Validator. Download all artifacts here.
I'll be back and edit this comment for each new commit.

❗ Run failed!

Download 'logs' artifact to see more details.

• master failed in: make_summary
• prioritize-mamba failed in: make_summary

Model Metrics

Benchmarks

Comparing prioritize-mamba (a44e01d) with master (e25c8ff).
Branch is 3 commits ahead and 1 commits behind.
Last updated on 2024-12-19 14:51:08 CET.

[lkstrp]

Just added an option to keep conda prioritised. I couldn't find a nice way to activate the environment. It is possible (see here), but some PATHS would still be missing after activation, and we don't want to fix a shell/ os/ conda vs. mamba

[FabianHofmann]

sure thing, how would I prefer conda? passing it as an argument?

[lkstrp]

export PYPSA_PREFER_CONDA=true in your .zshrc/ .bashrc

[FabianHofmann]

perfect!