This release is a pre-release and may not be stable for production use.
amiclimate
NLP and semantic software and material for managing climate knowledge
Python code for accessing and transforming key climate documents. A refactoring of the (bloated) pyamihtml repository. Will initially have functionality for downloading and parsing
- IPCC reports
- IPCC glossary
- UNFCCC reports (COP, etc.)
This requires bespoke library routines and these are available in a new amilib repository.
This repository will NOT have the complete IPCC or UNFCCC corpus , but will have small exemplars.
tests
Applications are developed as tests, and then factored into command
Metadata
Release files for amiclimate 0.0.1a2
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 |
|---|---|---|---|---|
| amiclimate-0.0.1a2.tar.gz | 72.8 kB | Without provenance | Details for amiclimate-0.0.1a2.tar.gz |
Release files / amiclimate-0.0.1a2.tar.gz
| Download URL | amiclimate-0.0.1a2.tar.gz |
|---|---|
| Size | 72.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4b6f528ddb939e268956645c127d58565812dd926f067b72a69812befa11c61f
|
|
BLAKE2b-256 checksum How to use checksums |
86cdeeaafc8e863dfc0f4e085cc144cd687caee0264585d91ec45440dfb53f64
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/7.1.0 pkginfo/1.10.0 requests/2.31.0 requests-toolbelt/1.0.0 tqdm/4.66.2 CPython/3.8.3
|
Security for amiclimate 0.0.1a2
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.