pynetcf
Basic python classes that map to netCDF files on disk written according to the Climate and Forecast metadata conventions
This is a first draft which has a lot of room for improvements, this is especially true for the time series based representations.
Citation
If you use the software in a publication then please cite it using the Zenodo DOI. Be aware that this badge links to the latest package version.
Please select your specific version at https://doi.org/10.5281/zenodo.846767 to get the DOI of that version. You should normally always use the DOI for the specific version of your record in citations. This is to ensure that other researchers can access the exact research artefact you used for reproducibility.
You can find additional information regarding DOI versioning at http://help.zenodo.org/#versioning
Installation
This package should be installable through pip:
pip install pynetcf
Contribute
We are happy if you want to contribute. Please raise an issue explaining what is missing or if you find a bug. We will also gladly accept pull requests against our master branch for new features or bug fixes.
Development setup
For Development we also recommend a conda environment. You can create one including test dependencies and debugger by running conda env create -f environment.yml. This will create a new pynetcf environment which you can activate by using source activate pynetcf.
Guidelines
If you want to contribute please follow these steps:
Fork the pynetcf repository to your account
make a new feature branch from the pynetcf master branch
Add your feature
Please include tests for your contributions in one of the test directories. We use py.test so a simple function called test_my_feature is enough
submit a pull request to our master branch
Note
This project has been set up using PyScaffold 4.2.3. For details and usage information on PyScaffold see https://pyscaffold.org/.
Metadata
Release files for pynetcf 0.5.2
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 |
|---|---|---|---|---|
| pynetcf-0.5.2.tar.gz | 41.5 kB | Without provenance | Details for pynetcf-0.5.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pynetcf-0.5.2-py3-none-any.whl | Python 3 | none | any | Details for pynetcf-0.5.2-py3-none-any.whl |
Total release size: 67.5 kB
Release files / pynetcf-0.5.2.tar.gz
| Download URL | pynetcf-0.5.2.tar.gz |
|---|---|
| Size | 41.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
da15b9e231698f125c4d8b17daf8ae81193948d343737b2d2c18441dd7c381ad
|
|
BLAKE2b-256 checksum How to use checksums |
a3bbb503ea8c0e26baaa8c268cb989a58b146cb9fb69c62292779359853c52dc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Release files / pynetcf-0.5.2-py3-none-any.whl
| Download URL | pynetcf-0.5.2-py3-none-any.whl |
|---|---|
| Size | 26.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8257d7e1e2156686dc09e4a61023d6ac3ef88c67ee413c5a7be97cd50ffef932
|
|
BLAKE2b-256 checksum How to use checksums |
89215a816d79b8befc766aa68a23408065c22cc17495e5423d4f1dd5fc7fc7bb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Security for pynetcf 0.5.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.