Subdomain helpers for the Django framework, including subdomain-based URL routing and reversing.
Full documentation can be found here: http://django-subdomains.readthedocs.org/
Build Status
Tested on Python 2.6, 2.7, 3.4 and 3.5 on their supported Django versions from 1.4 through 1.9.
Metadata
Release files for django-subdomains 2.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 | |
|---|---|---|---|---|
| django-subdomains-2.1.0.tar.gz | 7.3 kB | Without provenance | Details |
Release files / django-subdomains-2.1.0.tar.gz
| Download URL | django-subdomains-2.1.0.tar.gz |
|---|---|
| Size | 7.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5684bb3a731de2295a549f6f2c3d6a806da802ff1ad369babd57cf008d9a783f
|
|
BLAKE2b-256 checksum How to use checksums |
93a6f1e60ee5e3df31d960fb3ad52f14ff068e15f150779b79bb77f38ea52c51
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-subdomains 2.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.