test-conda/README.md

# Conda environment with environment.yml

[![Binder](http://mybinder.org/badge_logo.svg)](http://mybinder.org/v2/gh/binder-examples/conda_environment/master?filepath=index.ipynb)

A Binder-compatible repo with an `environment.yml` file.

Access this Binder by clicking the blue badge above or at the following URL:

http://mybinder.org/v2/gh/binder-examples/conda_environment/master?filepath=index.ipynb

## Notes
The `environment.yml` file should list all Python libraries on which your notebooks
depend, specified as though they were created using the following `conda` commands:

```
conda activate example-environment
conda env export --from-history -f environment.yml
```

Note that the only libraries available to you will be the ones specified in
the `environment.yml`, so be sure to include everything that you need! 

Also note that if you skip the `--from-history`, conda may include OS-specific
packages in `environment.yml`, which you would have to manually prune from
`environment.yml`.  For example, confirmed macOS-specific packages that should
be removed are:

* libcxxabi=4.0.1
* appnope=0.1.0
* libgfortran=3.0.1
* libcxx=4.0.1
s/Anaconda/conda/ We don't make anaconda available 2017-11-17 23:39:52 +00:00			`# Conda environment with environment.yml`
first move 2017-07-24 20:33:10 +00:00
Update README.md 2019-11-24 17:39:39 +00:00			`[![Binder](http://mybinder.org/badge_logo.svg)](http://mybinder.org/v2/gh/binder-examples/conda_environment/master?filepath=index.ipynb)`
first move 2017-07-24 20:33:10 +00:00
Update README.md 2017-11-03 04:03:38 +00:00			A Binder-compatible repo with an `environment.yml` file.

Update README.md 2020-02-06 13:34:46 +00:00			`Access this Binder by clicking the blue badge above or at the following URL:`
first move 2017-07-24 20:33:10 +00:00
Update README.md 2019-11-24 17:40:33 +00:00			`http://mybinder.org/v2/gh/binder-examples/conda_environment/master?filepath=index.ipynb`
first move 2017-07-24 20:33:10 +00:00
Update README.md 2017-11-03 05:39:14 +00:00			`## Notes`
first move 2017-07-24 20:33:10 +00:00			The `environment.yml` file should list all Python libraries on which your notebooks
			depend, specified as though they were created using the following `conda` commands:

			```
Update README.md 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. 2020-06-29 19:46:05 +00:00			`conda activate example-environment`
			`conda env export --from-history -f environment.yml`
first move 2017-07-24 20:33:10 +00:00			```

			`Note that the only libraries available to you will be the ones specified in`
Update README.md 2019-03-02 19:32:37 +00:00			the `environment.yml`, so be sure to include everything that you need!

Update README.md 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. 2020-06-29 19:46:05 +00:00			Also note that if you skip the `--from-history`, conda may include OS-specific
			packages in `environment.yml`, which you would have to manually prune from
			`environment.yml`. For example, confirmed macOS-specific packages that should
			`be removed are:`
Update README.md 2019-03-02 19:32:37 +00:00
			`* libcxxabi=4.0.1`
			`* appnope=0.1.0`
			`* libgfortran=3.0.1`
			`* libcxx=4.0.1`