Django-guardian

=========================

* Official Django 1.8 support (thanks to multiple contributors)

============================

* Official Django 1.7 support (thanks Troy Grosfield and Brian May)
* Allow to override ``PermissionRequiredMixin.get_permission_object``, part
of ``PermissionRequiredMixin.check_permissions`` method, responsible for
retrieving single object (Thanks zauddelig)
* French translations (Thanks Morgan Aubert)
* Added support for ``User.get_all_permissions`` (thanks Michael Drescher)

============================

* Fixed another issue with custom primary keys at admin extensions (Thanks Omer
Katz)

============================

Unfortunately this was broken release not including any important changes.

===========================

* Fixed issue with custom primary keys at admin extensions (Thanks Omer Katz)
* ``get_403_or_None`` now accepts Python path to the view function, for example
``'django.contrib.auth.views.login'`` (Thanks Warren Volz)
* Added ``with_superuser`` flag to ``guardian.shortcuts.get_objects_for_user``
(Thanks Bruno Ribeiro da Silva)
* Added possibility to disable monkey patching of the ``User`` model.
(Thanks Cezar Jenkins)

=========================

* Removed ``get_for_object`` methods from managers (188)
* Extended documentation
* GuardedModelAdmin has been splitted into mixins
* Faster queries in get_objects_for_user when use_groups=False or any_perm=True
(148)
* Improved speed of get_objects_for_user shortcut
* Support for custom User model with not default username field
* Added GUARDIAN_GET_INIT_ANONYMOUS_USER setting (179)
* Added ``accept_global_perms`` to ``PermissionRequiredMixin``
* Added brazilian portuguese translations
* Added polish translations
* Added ``wheel`` support
* Fixed wrong anonymous user checks
* Support for Django 1.6
* Support for Django 1.7 alpha

.. important::
In this release we have removed undocumented ``get_for_object`` method
from both ``UserObjectPermissionManager`` and
``GroupObjectPermissionManager``. Not deprecated, removed. Those methods
were not used within ``django-guardian`` and their odd names could lead to
issues if user would believe they would return object level permissions
associated with user/group and object passed as the input. If you depend
on those methods, you'd need to stick with version 1.1 and make sure you
do not misuse them.