Development guide¶
This tutorial will guide you through setting up a working environment for developing nyaml.
What should you know before this tutorial?¶
- You should read Tutorials > Installation.
What you will know at the end of this tutorial?¶
You will know
- how to set up your environment for developing
nyaml - how to make changes to the software
- how to test the software
- how to contribute on GitHub
Contributing¶
Structure of the nyaml repository
The software tools are located inside src/nyaml. They are shipped with unit tests located in tests.
Setup¶
It is recommended to use Python 3.11+ with a dedicated virtual environment for this package. Learn how to manage Python versions and virtual environments. We recommend using uv, an extremely fast Python package and project manager. In this tutorial, you will find parallel descriptions using either uv or a more classical approach using venv and pip.
Start by creating a virtual environment:
That command creates a new virtual environment in a directory called .venv.
Development installation¶
We start by cloning the repository:
Next, we install the package in editable mode (together with its dependencies):Linting and formatting¶
We are using ruff and mypy for linting, formatting, and type checking. It is recommended to use the pre-commit hook available for ruff, which formats the code and checks the linting before making a Git commit.
Install the pre-commit hook by running
from the root of this repository.
Testing¶
There exist unit tests for the software written in pytest, which can be used as follows:
Editing the documentation¶
We are using MkDocs for the documentation. If you edit the documentation, you can build it locally. For this, you need to install an additional set of dependencies:
You can then serve the documentation locally by running
Contributing to the package on GitHub¶
Once you are happy with the changes, please commit them on a feature branch on a fork of the original repository and create a pull request on GitHub. We run a number of GitHub Actions that check code formatting and linting, run the tests in an isolated environment, and build the documentation. Once these actions pass and a peer review of the code has occurred, your code will be accepted.
Reporting issues and seeking support¶
If you face any issues with the tool or when setting up the development environment, please create a new GitHub issue.
For general questions or support, see our contact page or join the NOMAD Discord channel.