It looks like it may be possible to just use a setting variable in
`contrib.auth.management` to accomplish this.
Currently using this workaround: http://blog.nyaruka.com/adding-a-view-
permission-to-django-models
--
Ticket URL: <https://code.djangoproject.com/ticket/20605>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* needs_better_patch: => 0
* version: 1.5 => master
* needs_docs: => 0
* needs_tests: => 0
* stage: Unreviewed => Accepted
Comment:
I don't see a reason to object to this request, so marking as accepted.
And, 'view' permission is such a fundamental permission it is a bit
strange that isn't available by default. At least being able to add it if
needed would be a good thing...
A new global setting is likely going to be objected. Maybe after app-
loading refactor this will be easier to tackle... Or maybe there could be
some other API for adding permissions. For example, Permission model
contains list of default permissions + a method to add more to that list.
--
Ticket URL: <https://code.djangoproject.com/ticket/20605#comment:1>
Comment (by timgraham):
#25087 is a duplicate with a patch (but as a setting).
--
Ticket URL: <https://code.djangoproject.com/ticket/20605#comment:2>
* cc: me@… (added)
--
Ticket URL: <https://code.djangoproject.com/ticket/20605#comment:3>