A middle to get the request from anywhere.
It is inspired on the: django-contrib-requestprovider-1.0.1
Usage
Add the following middleware to setings.py:
- MIDDLEWARE_CLASSES=(
… ‘request_provider.middleware.RequestProvider’, … )
And when you require the request, just do:
from request_provider.signals import get_request http_request = get_request()
1 maintainer
Metadata
1 maintainer
Release files for django-request-provider 1.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 | |
|---|---|---|---|---|
| django-request-provider-1.0.2.tar.gz | 2.3 kB | Without provenance | Details |
Release files / django-request-provider-1.0.2.tar.gz
| Download URL | django-request-provider-1.0.2.tar.gz |
|---|---|
| Size | 2.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ec400f19b8faa979daea249866c0c207155566c9ee1cf5c80ab6bac49f9dff04
|
|
BLAKE2b-256 checksum How to use checksums |
929040fbbe0aed548fb5268130bbd321e624bd01626f3f04a0776e98dea20a33
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-request-provider 1.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.
