Introduction
collective.subscribe contains components for associating users/principals as subsribers to an item of content, maintaining a relationship between them, and providing an index for such relationships.
This package provides underlying components that use and integrate with the Zope Component Architecture (ZCA), and can be used by higher-level packages providing application-specific uses of the adapters, entities, utilities, and indexes provided by this package.
Author: Sean Upton <sean.upton@hsc.utah.edu>
This package is released under an MIT license; see docs/COPYING.txt Copyright (c) 2011, The University of Utah
Changelog
0.1 (2012-08-04)
renamed from uu.subscribe to collective.subscribe for release as Plone Collective project.
Initial release.
2 maintainers
Metadata
2 maintainers
Release files for collective.subscribe 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 | Actions |
|---|---|---|---|---|
| collective.subscribe-0.1.zip | 30.2 kB | Without provenance | Details for collective.subscribe-0.1.zip |
Release files / collective.subscribe-0.1.zip
| Download URL | collective.subscribe-0.1.zip |
|---|---|
| Size | 30.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3df5347de3d8e5530d22de49b6f09cddbc8e102f9c4b594609676354c4abf07e
|
|
BLAKE2b-256 checksum How to use checksums |
997eb67e860aa9648d7694bf7c198067d2280d7065163dc7e289de704d281a75
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.subscribe 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
