Podiant notifications
A set of models, views and templates for creating and managing user notifications
Quickstart
Install Notifications:
pip install podiant-notifications
Add it to your INSTALLED_APPS:
INSTALLED_APPS = (
...
'notifications',
...
)
Add Notifications' URL patterns:
from notifications import urls as notifications_urls
urlpatterns = [
...
url(r'^', include(notifications_urls)),
...
]
Running tests
Does the code actually work?
coverage run --source notifications runtests.py
Credits
Tools used in rendering this package:
1 maintainer
Metadata
1 maintainer
Release files for podiant-notifications 1.1.0
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 | |
|---|---|---|---|---|
| podiant-notifications-1.1.0.tar.gz | 7.5 kB | Without provenance | Details |
Release files / podiant-notifications-1.1.0.tar.gz
| Download URL | podiant-notifications-1.1.0.tar.gz |
|---|---|
| Size | 7.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cd2acf01eb66f8edd8ab355855354368424fef23daf6cd605c28d5cf614d9ddb
|
|
BLAKE2b-256 checksum How to use checksums |
fb5ca5b3c72f47bc35d49d80ea1b8b074e9230b065accad710a2b267b39058b1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.8.0 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.6.3
|
Security for podiant-notifications 1.1.0
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.
