Skip to content
This repository has been archived by the owner on Nov 14, 2023. It is now read-only.

Use conda env with pinned packages in release #25

Open
cehbrecht opened this issue Feb 25, 2019 · 1 comment
Open

Use conda env with pinned packages in release #25

cehbrecht opened this issue Feb 25, 2019 · 1 comment
Assignees
@cehbrecht
Labels
enhancement New feature or request
Milestone
0.3.0

Comments

@cehbrecht
Copy link
Collaborator

Description

Conda environments have the tendency to break (cdo/netcdf/hdf from conda-forge). To make conda envs more stable and reproducible we can use pinned packages:

https://conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#building-identical-conda-environments

Environment

  • c4cds-wps version used, if any:
  • Python version, if any:
  • Operating System:

Steps to Reproduce

Additional Information
@cehbrecht cehbrecht added the enhancement New feature or request label Feb 25, 2019
@cehbrecht cehbrecht added this to the 0.3.0 milestone Feb 25, 2019
@cehbrecht cehbrecht self-assigned this Feb 25, 2019
@cehbrecht
Copy link
Collaborator Author

I have updated the spec-file.txt from a working environment.

You can install it with:

$ conda create --name c4cds --file spec-file.txt

OR

$ conda install --name c4cds --file spec-file.txt

@cehbrecht cehbrecht mentioned this issue Feb 27, 2019
Closed
@cehbrecht cehbrecht mentioned this issue Mar 11, 2019
Open
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@cehbrecht cehbrecht

Labels
enhancement New feature or request
Projects
None yet
Milestone
0.3.0
Development

No branches or pull requests
1 participant
@cehbrecht