PyCDS is a Python package that provides an Object Relational Mapping (ORM) layer for accessing meteorological observations stored in a relational database in a standard database model, referred to variously as a CRMP database or a PCDS database.

This package uses Alembic to manage database creation and migration. For details, see Database operations with Alembic, below.

This type of database (PCDS/CRMP schema) is currently used at PCIC to store BC's long-term weather archive, the Provincial Climate Data Set (PCDS), and the Northern Climate Database (Metnorth). For details, see Background.

With this package, one can recreate the database schema in a PostgreSQL or SQLite database and/or use the package as an object mapper for programmatic database access. PyCDS uses SQLAlchemy to provide the ORM layer.

• Background
• Installation
• Scripts
• ORM contents and usage
• Database operations with Alembic
  • Introduction
  • Applying a migration: Upgrade
  • Applying a migration: Downgrade
  • Creating a new PyCDS database
• Testing
  • Project unit tests
  • Test migrations with a test database
  • Unit tests in client code
• Development
  • Migrations
    • Introduction
    • IMPORTANT ADVICE AND GUIDELINES
    • Creating a new migration
    • Creating the initial migration
  • Creating and using SQLAlchemy extensions
  • Creating and using Alembic extensions

TOC courtesy of Lucio Paiva.

Below we describe incrementing the package version manually. We could consider using the command poetry version instead to get Poetry to do it for us.

1. Modify tool.poetry.version in pyproject.toml: First remove any suffix to the version number, as our convention is to reserve those for test builds (e.g., 1.2.3 is a release build, 1.2.3.dev7 is a test build). Then increment the release build version.
2. Summarize release changes in NEWS.md
3. Commit these changes, then tag the release

   git add pyproject.toml NEWS.md
   git commit -m"Bump to version X.Y.Z"
   git tag -a -m"X.Y.Z" X.Y.Z
   git push --follow-tags

4. Our GitHub Action pypi-publish.yml will build and release the package on our PyPI server.

The process is very similar to a production release, but uses a different version number convention, and omits any notice in NEWS.md.

1. Modify tool.poetry.version in pyproject.toml: Add or increment the suffix in the pattern .devN, where N is any number of numeric digits (e.g., 1.2.3.dev11). Our convention is to reserve those for test releases (e.g., 1.2.3 is a release build, 1.2.3.dev11 is a test build).
2. Commit changes and tag the release:

   git add pyproject.toml
   git commit -m"Create test version X.Y.Z.devN"
   git tag -a -m"X.Y.Z.devN" X.Y.Z.devN
   git push --follow-tags

3. Our GitHub Action pypi-publish.yml will build and release the package on our PyPI server.