Skip to content

Conversation

@moble
Copy link
Contributor

@moble moble commented Jun 29, 2020

Two small — though important — changes

  1. Since the release of conda 4.6, the recommended way to activate a conda env is to use conda activate <myenv>.
  2. The conda docs say that the correct way to export an env is to use the --from-history flag. This only includes packages that you’ve explicitly asked for, and only "pins" versions when you asked to do so. If you use this flag, the "macOS-specific" packages probably won't appear.

I'm actually of the opinion that the list of macOS-specific packages should be removed, but I'll leave them here because other people don't seem to agree — though in any case, I don't see why those packages' versions should be relevant. See also #11.

Two small — though important — changes

  1. Since [the release of conda 4.6](https://www.anaconda.com/blog/conda-4-6-release), the [recommended way to activate a conda env](https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#activating-an-environment) is to use `conda activate <myenv>`.
  2. The [conda docs say](https://conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#exporting-an-environment-file-across-platforms) that the correct way to export an env is to use the `--from-history` flag.  This only includes packages that you’ve explicitly asked for, and only "pins" versions when you asked to do so.  If you use this flag, the "macOS-specific" packages probably won't appear.
@choldgraf
Copy link
Contributor

This is great - many thanks for the fix 👍

@choldgraf choldgraf merged commit 5778653 into binder-examples:master Jun 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants