#11154: Inconsistency with permissions for proxy models
------------------------------+------------------------------------
Reporter: etianen | Owner: nobody
Type: Bug | Status: new
Component: contrib.auth | Version: SVN
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 1
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------+------------------------------------
Comment (by charettes):
Replying to [comment:38 danny.adair@…]:
> Replying to [comment:37 charettes]:
> >[...]
> > Defaulting {{{ follow_proxy }}} (like that one :) to `False` would
unify both API but would break backward compatibility.
> >[...]
> > I ran the test with {{{ follow_proxy=False }}} as default and only
[http://dpaste.com/hold/697615/ two tests breaks]. However apps relying on
`contrib.ContentType` in the wild could break badly.
> > [...]
> > We can either break the API to unite them or offer the user to ''opt-
in'' in order to maintain backward compatibility. But this whole
discussion is getting bigger then the ticket itself. We should maybe open
another issue to fix the `ContentType` proxy issue that blocks this one
and then, once it's fixed, use the new hooks to fix this one with:
>
> I agree an implementation in two steps would help everyone (and faster
to get checked in).
> Just want to point out that if you consider this a bug (like I do) then
backwards-compatibility (= keep software happy that relies on the bug) is
a less strong argument for retaining it. Right the wrong or continue its
adoption? django-reversion is _currently_ broken.
I'm in the process of writing a new ticket describing the issue in which
I'll suggest a design decision is taken toward breaking backward
compatibility.
--
Ticket URL: <https://code.djangoproject.com/ticket/11154#comment:39>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
