Developer environments
======================

For developers in the Met Office, there is an existing developer environment and
module that can be used.
This environment is kept up to date for the current state of main.

For external developers, an environment can be created following the
:external+ants:ref:`ANTS installation instructions <install>`.

If a change in the environment is needed, the ``environment.yml`` file in the
branch should be updated and a new environment created from the changed
``environment.yml`` file.  From this environment, a lock file should be created
via:

.. code-block:: shell

    conda list --explicit > environment.lock

and then committed to the branch.  This process ensures that the MIAO team can
replicate the environment for a central deployment.

If you see different behaviour between the running tests in rose stem and your
normal environment, it's likely that you have some packages installed in your
user ``site-packages`` directory.  These are isolated depending on python
version, but not isolated to a particular conda environment.  The rose stem
workflow uses :external+ants:ref:`ants-launch <ants_launch>`
to ignore these `user installed packages
<https://github.com/MetOffice/ANTS/blob/main/bin/ants-launch#L61>`_.