Skip to content

Commit f84449c

Browse files
authored
Merge pull request #384 from ESMValGroup/update_development-setup_v2.13.0
Update "Development and contribution" episode for v2.13.0
2 parents b046d7b + 71a4102 commit f84449c

File tree

1 file changed

+8
-9
lines changed

1 file changed

+8
-9
lines changed

_episodes/07-development-setup.md

Lines changed: 8 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: "Development and contribution"
33
teaching: 10
44
exercises: 20
5-
compatibility: ESMValTool v2.9.0
5+
compatibility: ESMValTool v2.13.0
66

77
questions:
88
- "What is a development installation?"
@@ -116,11 +116,11 @@ following the lesson
116116
[Installation]({{ page.root }}{% link _episodes/02-installation.md %}),
117117
we should choose another name for the new environment in this lesson.
118118

119-
ESMValTool now uses `mamba` instead of `conda` for the recommended installation.
119+
ESMValTool uses `mamba` for the recommended installation.
120120
For a minimal mamba installation, see section **Install Mamba** in lesson
121121
[Installation]({{ page.root }}{% link _episodes/02-installation.md %}).
122122

123-
It is good practice to update the version of mamba and conda on your machine before
123+
It is good practice to update the version of mamba on your machine before
124124
setting up ESMValTool. This can be done as follows:
125125

126126
~~~bash
@@ -145,7 +145,8 @@ mamba env create --name a_new_name --file environment.yml
145145
This will create a new conda environment and install ESMValTool (with all
146146
dependencies that are needed for development purposes) into it with a single command.
147147

148-
For more information see [conda managing environments][manage-environments].
148+
For more information see
149+
[Mamba User Guide](https://mamba.readthedocs.io/en/latest/user_guide/mamba.html).
149150

150151
Now, we should activate the environment:
151152

@@ -179,9 +180,6 @@ If the installation is successful, ESMValTool prints a help message to the conso
179180
> the ``esmvaltool`` environment.
180181
> Use this command to check that ESMValTool is installed in a ``develop`` mode.
181182
>
182-
> **Tip**: see the
183-
> [documentation on conda list](https://docs.conda.io/projects/conda/en/latest/commands/list.html).
184-
>
185183
>> ## Solution
186184
>>
187185
>> Run:
@@ -202,7 +200,7 @@ If the installation is successful, ESMValTool prints a help message to the conso
202200
203201
The ``main`` branch has the latest features of ESMValTool. Please make sure
204202
that the source code on your machine is up-to-date. If you obtain the source
205-
code using git clone as explained in step **1 Source code**, you can run ``git pull``
203+
code using git clone as explained in section **1 Source code**, you can run ``git pull``
206204
to update the source code. Then ESMValTool installation will be updated
207205
with changes from the ``main`` branch.
208206
@@ -276,7 +274,8 @@ The good news is that ``pre-commit`` has been already installed
276274
when we chose development installation.
277275
``pre-commit`` is a command line and runs all of those tools. It also fixes some of those errors.
278276
To explore other tools, have a look at ESMValTool documentation on
279-
[Code style](https://docs.esmvaltool.org/en/latest/community/introduction.html#code-style).
277+
[Code quality](https://docs.esmvaltool.org/en/latest/community/
278+
code_documentation.html#code-quality).
280279
281280
> ## Using pre-commit
282281
>

0 commit comments

Comments
 (0)