From 6c18541781adce9171d2d0664aebed1682fe00a5 Mon Sep 17 00:00:00 2001 From: Andrew Gait Date: Tue, 21 Apr 2026 16:46:30 +0100 Subject: [PATCH 1/2] Update instructions to use conda export rather than conda env export --- episodes/04-software_package_management.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/episodes/04-software_package_management.md b/episodes/04-software_package_management.md index 9874dbb..51f293b 100644 --- a/episodes/04-software_package_management.md +++ b/episodes/04-software_package_management.md @@ -393,7 +393,7 @@ This contains similar information to the standard `conda list` command, but in a A better method is to use: ```bash -conda env export +conda export ``` ```output @@ -419,12 +419,12 @@ dependencies: prefix: /home/mbessdl2/.conda/envs/myenv ``` -This will present the same information, but in the more readable [YAML](https://yaml.org/) format, and it will also include the channel information in the output. This information can be saved as a text file as before, and used to create a new environment using the command `conda env create`. However it is still operating system specific information. +This will present the same information, but in the more readable [YAML](https://yaml.org/) format, and it will also include the channel information in the output. This information can be saved as a txt or yml file as before e.g. `conda export > envfile.yml`, and used to create a new environment using the command `conda env create` (see below). However it is still using operating system specific information. To create a higher-level record of the environment you can use: ```bash -conda env export --from-history +conda export --from-history ``` ```output @@ -462,7 +462,7 @@ The name that you give the environment does not have to be the same as the name - `conda install -n ` installs packages in a pre-existing environment - `conda activate ` activates the named environment, giving access to the software installed there - `conda deactivate` deactivates the current environment -- `conda env export --from-history > ` creates a portable record of your current environment +- `conda export --from-history > ` creates a portable record of your current environment - `conda env create --file ` creates a new environment from an environment file :::::::::::::::::::::::::::::::::::::::::::::::::: From e07c98dbcc5cf8e86b19a776e30053279fc9c0de Mon Sep 17 00:00:00 2001 From: Andrew Gait Date: Wed, 22 Apr 2026 11:36:57 +0100 Subject: [PATCH 2/2] Add explicit output to yml file for export --- episodes/04-software_package_management.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/episodes/04-software_package_management.md b/episodes/04-software_package_management.md index 51f293b..315e6de 100644 --- a/episodes/04-software_package_management.md +++ b/episodes/04-software_package_management.md @@ -424,7 +424,8 @@ This will present the same information, but in the more readable [YAML](https:// To create a higher-level record of the environment you can use: ```bash -conda export --from-history +conda export --from-history > envfile.yml +more envfile.yml ``` ```output