Closed jkikstra closed 1 month ago
That sounds like you did not install the conda environment from environment.yml
You're right. And you're also right that that's is the way that it is currently supported - according to the readme.
I was doing it using poetry
(when I was creating an environment for emissions_harmonization_historical), which I suppose looks at the pyproject.toml, which I think is out of sync?
It does look at that, but it's more by design than mistake. pyproject and pip/poetry and consorts in general have a very bad track record of working with anything that involves geospatial analysis around the gdal and osgeo libraries. It is in my experience safer to always manage environments with conda/mamba for those analyses. If zeb or others say that is no longer the case, i would be open to including them in pyproject.toml, but a few years back this has caused hard to debug headaches.
Nah all good @coroa thanks. We'll switch to pixi
Okidokes, so then I suppose this issue can be closed.
@znichollscr Thanks. pixi looks very helpful.
Glad it helps. If you're interested, our default environment managers are now basically:
In both cases, we use pdm as the build backend because it has some features we like, like locked builds (this repo basically demonstrates it https://github.com/openscm/openscm-zenodo). I reckon that uv will have their own version of this pretty soon, at which point we might stop using pdm.
dask
distributed
colorlog