Overview
The p4a.image package provides a framework for handling image content on the Zope 2 and Zope 3 platforms. It was inspired by the Plone ATPhoto product its sibling p4a products.
Developer Notes
Maintainer
David Siedband (technique at occeanicsky dot com) is the active maintainer of the p4a.image framework.
2 maintainers
Metadata
2 maintainers
Release files for p4a.image 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.image-0.2.tar.gz | 2.9 MB | Without provenance | Details |
Release files / p4a.image-0.2.tar.gz
| Download URL | p4a.image-0.2.tar.gz |
|---|---|
| Size | 2.9 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
76f43025083f530230acf526868b4445f721f36833f877529f663f3c23df5fd1
|
|
BLAKE2b-256 checksum How to use checksums |
356f2150f76eed456ece6b113f3eb5937c52b60aeb3c6c60b725b567921d3505
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for p4a.image 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.
