Update django-guardian settings #4871
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report
@@ Coverage Diff @@
## master #4871 +/- ##
=======================================
Coverage 76.47% 76.47%
=======================================
Files 158 158
Lines 9993 9993
Branches 1262 1262
=======================================
Hits 7642 7642
Misses 2009 2009
Partials 342 342 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
RTD is using django-guardian (version: 1.4.9).
ANONYMOUS_USER_IDis deprecated (changelog) in1.4.2According to the new configurable variables, we should use
ANONYMOUS_USER_NAME, whose default value is already set to"AnonymousUser"(Read here). So, I think that there is no need to set it again in oursettings/base.py