django-rest-messaging
The project provides a Facebook-like messaging API for django rest framework.
Requirements
Python (2.7, 3.3, 3.4)
Django (1.6, 1.7, 1.8)
Django REST Framework (2.4, 3.0, 3.1)
Installation
Install using pip…
$ pip install django-rest-messaging
Example
TODO: Write example.
Testing
Install testing requirements.
$ pip install -r requirements.txt
Run with runtests.
$ ./runtests.py
You can also use the excellent tox testing tool to run the tests against all supported versions of Python and Django. Install tox globally, and then simply run:
$ tox
Documentation
To build the documentation, you’ll need to install mkdocs.
$ pip install mkdocs
To preview the documentation:
$ mkdocs serve
Running at: http://127.0.0.1:8000/
To build the documentation:
$ mkdocs build
Metadata
Release files for django-rest-messaging 1.0.3
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 | |
|---|---|---|---|---|
| django-rest-messaging-1.0.3.tar.gz | 11.5 kB | Without provenance | Details |
Release files / django-rest-messaging-1.0.3.tar.gz
| Download URL | django-rest-messaging-1.0.3.tar.gz |
|---|---|
| Size | 11.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1616f38329aefc1df3ad9690823dd2b14b1345bba7f47dead46a579b9d88b656
|
|
BLAKE2b-256 checksum How to use checksums |
635aa22d25ed24419d1629eb3da2f3705ebb985c1b5795c0dfa4479df36d5247
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-rest-messaging 1.0.3
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.