ESA PDS4 Packager
Documentation: https://luca-penasa.github.io/esa-pds4-packager
Source Code: https://github.com/luca-penasa/esa-pds4-packager
PyPI: https://pypi.org/project/esa-pds4-packager/
Installation
pip install esa-pds4-packager
Development
- Clone this repository
- Requirements:
- uv
- Python 3.10+
- Create a virtual environment and install the dependencies
uv sync
Testing
uv run pytest
Documentation
The documentation is automatically generated from the content of the docs directory and from the docstrings of the public signatures of the source code. The documentation is updated and published as a Github Pages page automatically as part each release.
Releasing
Manual release
Releases are done with the command, e.g. incrementing patch:
uv run just bump patch
# also push, of course:
git push origin main --tags
this will update the changelog, commit it, and make a corresponding tag.
as the CI is not yet configured for publish on pypi it can be done by hand:
uv build
uv publish --build path/to/wheel
Automatic release - to be fixed
Trigger the Draft release workflow (press Run workflow). This will update the changelog & version and create a GitHub release which is in Draft state.
Find the draft release from the GitHub releases and publish it. When a release is published, it'll trigger release workflow which creates PyPI release and deploys updated documentation.
Updating with copier
To update the skeleton of the project using copier:
uvx copier update --defaults
Pre-commit
Pre-commit hooks run all the auto-formatting (ruff format), linters (e.g. ruff and mypy), and other quality
checks to make sure the changeset is in good shape before a commit/push happens.
You can install the hooks with (runs for each commit):
pre-commit install
Or if you want them to run only for each push:
pre-commit install -t pre-push
Or if you want e.g. want to run all checks manually for all files:
pre-commit run --all-files
This project was generated using a fork of the wolt-python-package-cookiecutter template.
Metadata
Release files for esa-pds4-packager 0.0.1
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 | |
|---|---|---|---|---|
| esa_pds4_packager-0.0.1.tar.gz | 7.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| esa_pds4_packager-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 16.2 kB
Release files / esa_pds4_packager-0.0.1.tar.gz
| Download URL | esa_pds4_packager-0.0.1.tar.gz |
|---|---|
| Size | 7.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
84b6e1d362a8ff6f0ed165956f7eee19d864bcd24febc33923fed9c8aa6fcc20
|
|
BLAKE2b-256 checksum How to use checksums |
af13219435c85424dcfbc2d04b1101b2b2b0a953bd7793f374510ba6a71bb8c0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.7.20
|
Release files / esa_pds4_packager-0.0.1-py3-none-any.whl
| Download URL | esa_pds4_packager-0.0.1-py3-none-any.whl |
|---|---|
| Size | 8.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
44dbba6d4734e62f5068a14c15e8045845af3333376ef2539243500ee65a7c52
|
|
BLAKE2b-256 checksum How to use checksums |
6498062ae07db0a5b86698a966087feaaa86cf987860a0c11d458f894c19d67a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.7.20
|
Security for esa-pds4-packager 0.0.1
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.