Adam Dobrawy

After looking at issues #396, #305 during creating a security release I have doubts that I have not rushed too much to accept the change and this is not the...

> @ad-m Does this change only effect the admin integration? Or are their repercussions if using Django Guardian to modify object permissions through something like DRF? I perceive that this...

> At the end of the day, your gut feel may be the best and perhaps the change should be reverted and a clear warning in the docs be added...

The change changes the earlier behavior of the application, which was - taking into account previous discussions - was designed this way, which means that it is not just a...

> Although I have written some tests for django apps before, they are very time consuming, more than I have just now, and I have not experience with tox (wich...

I have created PR #764 to revert PR #757. I need make `master` right again to merge others PR eg. #763 . @areyal feel free to create a new PR...

We can also show the ecosystem in the form of libraries. To get started: - https://github.com/rpkilby/django-rest-framework-guardian

What do you want is not object-level permission, but model-level permission. Model-level permission is build-in in Django, so you do not need Django-guardian for that. If you really want to...

I'm not interested in making such contributions to the project personally as I don't use django-guardian actively (see #759). I participate in this project sporadically when I receive a notification...

I believe you should use: ```python from guardian.conf.settings import ANONYMOUS_USER_NAME print(ANONYMOUS_USER_NAME) ```` If you need access to django-guardian configuration option, along with the default values of django-guardian. The name of...