GHGA Metadata Utils
The GHGA Metadata Utils is a package that provides all things related to the GHGA Metadata Schema.
The repository is structured to encourage,
- reuse of custom generators
- manage validation plugins
Documentation:
An extensive documentation can be found here (coming soon).
Quick Start
Installation
# Execute in the repo's root dir:
pip install .
Development
For setting up the development environment, we rely on the devcontainer feature of vscode in combination with Docker Compose.
To use it, you have to have Docker Compose as well as vscode with its "Remote - Containers" extension (ms-vscode-remote.remote-containers) installed.
Then open this repository in vscode and run the command
Remote-Containers: Reopen in Container from the vscode "Command Palette".
This will give you a full-fledged, pre-configured development environment including:
- infrastructural dependencies of the service (databases, etc.)
- all relevant vscode extensions pre-installed
- pre-configured linting and auto-formating
- a pre-configured debugger
- automatic license-header insertion
Moreover, inside the devcontainer, there are two convenience commands available (please type them in the integrated terminal of vscode):
dev_install- install the service with all development dependencies, installs pre-commit, and applies any migration scripts to the test database (please run that if you are starting the devcontainer for the first time or if you added any python dependencies to the./setup.cfg)
If you prefer not to use vscode, you could get a similar setup (without the editor specific features) by running the following commands:
# Execute in the repo's root dir:
cd ./.devcontainer
# build and run the environment with docker-compose
docker-compose up
# attach to the main container:
# (you can open multiple shell sessions like this)
docker exec -it devcontainer_app_1 /bin/bash
License
This repository is free to use and modify according to the Apache 2.0 License.
Metadata
Release files for ghga-metadata-utils 0.0.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| ghga_metadata_utils-0.0.5.tar.gz | 13.7 kB | Without provenance | Details for ghga_metadata_utils-0.0.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ghga_metadata_utils-0.0.5-py3-none-any.whl | Python 3 | none | any | Details for ghga_metadata_utils-0.0.5-py3-none-any.whl |
Total release size: 35.4 kB
Release files / ghga_metadata_utils-0.0.5.tar.gz
| Download URL | ghga_metadata_utils-0.0.5.tar.gz |
|---|---|
| Size | 13.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cfacf24ecd0d94d92eae641b864a94d07b3067fd413f697bdf799346c7448568
|
|
BLAKE2b-256 checksum How to use checksums |
10b3e769015ffd3400b97df9b05e43ec00f285299980b094ae869d54f3b64e65
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.13
|
Release files / ghga_metadata_utils-0.0.5-py3-none-any.whl
| Download URL | ghga_metadata_utils-0.0.5-py3-none-any.whl |
|---|---|
| Size | 21.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a92e2310bf348e0bdc3c168c468fa1e0a21503685deebfbc5c43d24184371003
|
|
BLAKE2b-256 checksum How to use checksums |
a41032c60fb02c34e57141bbf0f9424d6a4ddbccd4cd8e18ea3d683d9b2d2751
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.13
|
Security for ghga-metadata-utils 0.0.5
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.