Validation of input4MIPs data (checking file formats, metadata etc.).

Key info :

PyPI :

Tests :

Other info :

• development: the project is actively being worked on

If you want to use openscm-zenodo as an application, for example you just want to use its command-line interface, then we recommend using the 'locked' version of the package. This version pins the version of all dependencies too, which reduces the chance of installation issues because of breaking updates to dependencies.

The locked version of openscm-zenodo can be installed with

=== "pip" sh pip install openscm-zenodo[locked]

[pip](https://pip.pypa.io/en/stable/)
is a standard way to install Python packages.

If you want to use openscm-zenodo as a library, for example you want to use it as a dependency in another package/application that you're building, then we recommend installing the package with the commands below. This method provides the loosest pins possible of all dependencies. This gives you, the package/application developer, as much freedom as possible to set the versions of different packages. However, the tradeoff with this freedom is that you may install incompatible versions of openscm-zenodo's dependencies (we cannot test all combinations of dependencies, particularly ones which haven't been released yet!). Hence, you may run into installation issues. If you believe these are because of a problem in openscm-zenodo, please raise an issue.

The (non-locked) version of openscm-zenodo can be installed with

=== "pip" sh pip install openscm-zenodo

[pip](https://pip.pypa.io/en/stable/)
is a standard way to install Python packages.
We make no guarantees that this will actually work
because pip's handling of the compiled dependencies
is not guaranteed.

Additional dependencies can be installed using

=== "pip" sh # To add notebook dependencies pip install openscm-zenodo[notebooks]

For development, we rely on pdm for all our dependency management. To get started, you will need to make sure that pdm is installed (instructions here, although we found that installing with pipx worked perfectly for us).

For all of our work, we use our Makefile. You can read the instructions out and run the commands by hand if you wish, but we generally discourage this because it can be error prone. In order to create your environment, run make virtual-environment.

If there are any issues, the messages from the Makefile should guide you through. If not, please raise an issue in the issue tracker.

For the rest of our developer docs, please see [development][development-reference].