-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add icepyx and other basic pangeo/pydata packages #4
Conversation
Bumps [conda-lock](https://github.com/conda-incubator/conda-lock) from 1.1.1 to 1.1.3. - [Release notes](https://github.com/conda-incubator/conda-lock/releases) - [Commits](conda/conda-lock@v1.1.1...v1.1.3)
Generated from running `cd conda/ && ./lock-environment.sh`. See also https://conda-incubator.github.io/conda-lock/output/#unified-lockfile
Compatible with conda/mamba installer. See also https://conda-incubator.github.io/conda-lock/output/#explicit-lockfile
Python tools for obtaining and working with ICESat-2 data! https://github.com/icesat2py/icepyx
So that binder and repo2docker can build the virtual environment with the correct dependencies (refer to https://mybinder.readthedocs.io/en/latest/introduction.html#what-is-a-binder on how the `binder/` folder works). Following uwhackweek template at https://github.com/uwhackweek/jupyterbook-template/blob/2022.04.08/binder/environment.yml
Tested this on binder, and
|
conda/conda-osx-64.lock.yml
Outdated
# Generated by conda-lock. | ||
# platform: osx-64 | ||
# input_hash: dd4cd8b2bfa13dad2a079f834ddc75bc178b28ecc4cb931ce6669470d2ec2619 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What are people's thoughts on having an OSX-specific lockfile? Do we need a conda-osx-64.lock.yml
file or could we remove it?
For the hackweeks, it made sense to have OSX (and possibly Windows) since the hackweek participants may want to install a virtual environment locally on their laptop. For the hosted Cryo JupyterHub though, it will just be using the Linux-built docker image, and I'm not sure if there's the expectation that users will be copying this environment locally?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Decided to remove the osx lockfile for now (see c274c75) to keep things minimal. Can always add it back later if requested.
Keeping it minimal and Linux-only for now.
Include more Cryosphere-focused packages (e.g.
icepyx
) in the docker image, and throw in a few others from the scientific Pangeo/PyData ecosystem.Once the
conda/environmen.yml
file is updated with new dependencies, the lockfiles (conda/conda-lock.yml
andconda/conda-linux-64.lock.yml
) are generated using:cd conda/ ./lock-environment.sh
TODO:
conda-lock
generated *.lock files used for reproducing the software environment exactlyicepyx
Continuation of #2, part of #1.