This release is a pre-release and may not be stable for production use.
Introduction
horae.notification provides persistent and email notifications for the Horae resource planning system.
Persistent notifications
Persistent notifications are displayed by a viewlet and a corresponding view. They are issued by adding new notifications (implementing horae.notification.interfaces.INotification to the notifications adapter registered for the interface horae.notification.interfaces.INotifications. Examples may be found in horae.notification.subscription and horae.planning.notification.
Email notifications
Email notifications are handled by using the horae.subscription package and are sent out to all subscribers of a ticket after it has changed.
Dependencies
Horae
Third party
System
horae.notification requires Pandoc a universal document converter to convert from HTML to reStructeredText to send the email notifications. Installation instructions for Pandoc may be found online at http://johnmacfarlane.net/pandoc/installing.html.
Changelog
1.0a1 (2012-01-16)
Initial release
1 maintainer
Metadata
1 maintainer
Release files for horae.notification 1.0a1
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 |
|---|---|---|---|---|
| horae.notification-1.0a1.tar.gz | 13.7 kB | Without provenance | Details for horae.notification-1.0a1.tar.gz |
Release files / horae.notification-1.0a1.tar.gz
| Download URL | horae.notification-1.0a1.tar.gz |
|---|---|
| Size | 13.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5ff5ad60298bc307b74eaf390d0b8d16058991ccb74001ceb50bd53cc747f6c3
|
|
BLAKE2b-256 checksum How to use checksums |
cf40635b97a62060272708ee1ed64bfb9c24fd2c5c1223c1153b3779cef131b1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for horae.notification 1.0a1
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.
