Django-roles-access

Latest version: v0.9.4

Safety actively analyzes 687918 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 2 of 2

0.8.4

Changed

- Unify README file in one README.md file.

- setup.py now got a new property long_description_content_type equal to
'text/markdown' letting markdown in Pypi.

0.8.3

Changed

- Documentation move it to: [Django roles access](https://django-roles-access.github.io)

- README file for Pypi.org.

- README.rst file for Github.com adding reference to Pypi.org and Travis

Added

- Configuration and integration with Travis-CI.org.

0.8.2

Changed

- License update to MIT LICENSE.

0.8.1

Added

- Updates in config file for updating to Pypi.org.

0.8

Changed
- As the name is already used at Pypi.org (`django-roles`), it is changed to
the new name `django-roles-access`.

0.7

Added
**Implement enhancements:**

- Start change log file.

- Add new configuration attribute **DJANGO_ROLES_FORBIDDEN_MESSAGE**. If not
defined default value is: `'<h1>403 Forbidden</h1>'`

- Add new configuration attribute **DJANGO_ROLES_REDIRECT**. Default behavior
when attribute has not been set, or is False, and user has no access
permission to the view: a
*django.http.HttpResponseForbidden(DJANGO_ROLES_FORBIDDEN_MESSAGE)* is
returned. When DJANGO_ROLES_REDIRECT is True what is returned is a
*django.http.HttpResponseRedirect(settings.LOGIN_URL)

Changed

- Change default behavior of raising PermissionDenied when user has no access
permission to the view. No more PermissionDenied is raised (see Added).

Page 2 of 2

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.