django-decorator-include
Include Django URL patterns with decorators.
Maintened by Twidi, on https://github.com/twidi/django-decorator-include based on the original work from Jeff Kistler on https://github.com/jeffkistler/django-decorator-include
Installation
Installation from Source
Unpack the archive, cd to the source directory, and run the following command:
python setup.py install
Installation with pip
Assuming you have pip installed, run the following command to install from PyPI:
pip install django-decorator-include
Installation with pip and git
Assuming you have pip and git installed, run the following command to install from the GitHub repository:
pip install git+git://github.com/twidi/django-decorator-include.git#egg=django-decorator-include
Requirements
The only required package is future, used for compatibility with python 2 and python 3
Usage
decorator_include is intended for use in URL confs as a replacement for the django.conf.urls.include function. It works in almost the same way as include, however the first argument should be either a decorator or an iterable of decorators to apply, in reverse order, to all included views. Here is an example URL conf:
from django.conf.urls import url
from django.contrib.auth.decorators import login_required
from decorator_include import decorator_include
urlpatterns = [
url(r'^$', 'mysite.views.index', name='index'),
url(r'^secret/', decorator_include(login_required, 'mysite.secret.urls'),
]
Running tests
If decorator_include is in the INSTALLE_APPS of your project, simply run:
django-admin test decorator_include
(you may want to use django-admin or ./manage.py depending on your installation)
If you are in a fresh virtualenv to work on decorator_include, install the django version you want:
pip install django
Then make the decorator_include module available in your python path. For example, with virtualenv-wrapper, considering you are at the root of the django-decorator-include repository, simply do:
add2virtualenv src
Or simply:
pip install -e .
Then to run the tests, this library provides a test project, so you can launch them this way:
DJANGO_SETTINGS_MODULE=decorator_include.tests.testproject.settings django-admin.py test decorator_include
Or simply launch the runtests.sh script (it will run this exact command):
./runtests.sh
Supported versions
Django version |
Python versions |
|---|---|
1.4, 1.5 |
2.6, 2.7 |
1.6 |
2.6, 2.7, 3.2, 3.3 |
1.7, 1.8 |
2.7, 3.2, 3.3, 3.4 |
1.9 |
2.7, 3.4, 3.5 |
Metadata
Release files for django-decorator-include 1.1
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 |
|---|---|---|---|---|
| django-decorator-include-1.1.tar.gz | 5.0 kB | Without provenance | Details for django-decorator-include-1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| django_decorator_include-1.1-py2-none-any.whl | Python 2 | none | any | Details for django_decorator_include-1.1-py2-none-any.whl |
Total release size: 14.1 kB
Release files / django-decorator-include-1.1.tar.gz
| Download URL | django-decorator-include-1.1.tar.gz |
|---|---|
| Size | 5.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
571f183599dbd7d1fc9caf2809157347f182c85b2536e9b979c1c87326cc5dfe
|
|
BLAKE2b-256 checksum How to use checksums |
957bb8c04bc9d2b7597d00938f6eb5f7fcfade5363639771285cb9b84ea0ae5b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / django_decorator_include-1.1-py2-none-any.whl
| Download URL | django_decorator_include-1.1-py2-none-any.whl |
|---|---|
| Size | 9.0 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
1184b1cdf6de1a7dd63d5c5a817c1d4b3fc83219c426f12da4a23d42199a6c5c
|
|
BLAKE2b-256 checksum How to use checksums |
06ecf291d86986300604894f054137b469324819f9593272c39dacc40cd296d4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-decorator-include 1.1
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.