cmip-branded-variable-mapper 0.7.1

Mapping from CMIP variable and other information to branded variable names.

CMIP Branded Variable Mapper

Mapping from CMIP variable and other information to branded variable names.

Key info :

PyPI :

Tests :

Other info :

Status

• prototype: the project is just starting up and the code is all prototype

Full documentation can be found at: cmip-branded-variable-mapper.readthedocs.io. We recommend reading the docs there because the internal documentation links don't render correctly on GitHub's viewer.

Installation

As an application

If you want to use CMIP Branded Variable Mapper as an application, 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 CMIP Branded Variable Mapper can be installed with

=== "pip" sh pip install 'cmip-branded-variable-mapper[locked]'

As a library

If you want to use CMIP Branded Variable Mapper 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 CMIP Branded Variable Mapper'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 CMIP Branded Variable Mapper, please raise an issue.

The (non-locked) version of CMIP Branded Variable Mapper can be installed with

=== "pip" sh pip install cmip-branded-variable-mapper

For developers

For development, we rely on uv for all our dependency management. To get started, you will need to make sure that uv is installed (instructions here (we found that the self-managed install was best, particularly for upgrading uv later).

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].

Original template

This project was generated from this template: copier core python repository. copier is used to manage and distribute this template.