p4a.ploneaudio
Overview
The p4a.ploneimage package is an integration component for integrating the p4a.image framework onto the Plone platform. It was inspired by the Plone ATPhoto product and its sibling p4a content types.
Maintainer
David Siedband (technique at oceanicsky dot com) is the active maintainer of the p4a.ploneimage component.
2 maintainers
Metadata
2 maintainers
Release files for p4a.ploneimage 0.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 | |
|---|---|---|---|---|
| p4a.ploneimage-0.2.tar.gz | 24.3 kB | Without provenance | Details |
Release files / p4a.ploneimage-0.2.tar.gz
| Download URL | p4a.ploneimage-0.2.tar.gz |
|---|---|
| Size | 24.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ec24e876702d6d5360024bb6936d72b01fcf722f0594c3f91cb6f98dead83cf8
|
|
BLAKE2b-256 checksum How to use checksums |
8773c803587ec775eef52e8b991755df1baffe851dab3824313e4dd85a160311
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for p4a.ploneimage 0.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.
