Skip to main content

umep-reqs

A minimal Python package outlining UMEP dependencies.

Installation

pip install umep-reqs

Version Management

This package uses setuptools_scm for automatic versioning based on Git tags. The package version is automatically determined from the latest Git tag.

How to Update Dependencies

When a new version of SuPy or other dependencies is released:

  1. Update the dependency version in pyproject.toml:

    dependencies = [
        "supy==2025.6.2.dev0",  # Update this version number
        "numba==0.59.0",
        # ... other dependencies
    ]
    
  2. Commit your changes:

    git add pyproject.toml
    git commit -m "Update SuPy to version X.X.X"
    
  3. Create a new release tag:

    git tag 2.6  # Use the next version number
    git push origin main
    git push origin 2.6
    
  4. The CI/CD pipeline will automatically:

    • Build the package with the new dependencies
    • Publish to Test PyPI (for all pushes)
    • Publish to PyPI (for tagged releases)
    • Create a GitHub release

Important Notes

  • DO NOT manually update version numbers in code - they are managed by Git tags
  • All dependency updates should be made in pyproject.toml
  • The setup.py file has been removed in favour of modern pyproject.toml configuration
  • Version numbers follow semantic versioning (MAJOR.MINOR.PATCH)

Metadata

Release files for umep-reqs 4.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for umep-reqs 4.2
File Size Uploaded Provenance Actions
umep_reqs-4.2.tar.gz 2.3 kB Without provenance Details for umep_reqs-4.2.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for umep-reqs 4.2
File Interpreter ABI Platform Actions
umep_reqs-4.2-py3-none-any.whl Python 3 none any Details for umep_reqs-4.2-py3-none-any.whl

Total release size: 4.3 kB

Release files / umep_reqs-4.2.tar.gz

Download URL umep_reqs-4.2.tar.gz
Size 2.3 kB
Tags Source
SHA-256 checksum
How to use checksums
76c0b53ae6925296824931f52ac489aa0d330ea79db3ad08e85add9dc628ec32
BLAKE2b-256 checksum
How to use checksums
598f0e3c4c1d04d1b1ac15b97e479199dd400cb6d8ed4f0993dfd3786926af12
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.1.0 CPython/3.12.8

Release files / umep_reqs-4.2-py3-none-any.whl

Download URL umep_reqs-4.2-py3-none-any.whl
Size 2.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
cd3e07d1556b49ce1200a76c62d46ea195de0688fb796fb89094df9efe84e808
BLAKE2b-256 checksum
How to use checksums
b45236621a515e39f8670026756295181d52f4fea0ae44f25eac5fea58dc9d50
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.1.0 CPython/3.12.8

Security for umep-reqs 4.2

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page