#28931: Non-conflicting `related_name` and `related_query_name` for `groups` and
`user_permissions` columns in `PermissionsMixin`
-------------------------------------+-------------------------------------
Reporter: Saiteja Parsi | Owner: Saiteja
Type: | Parsi
Cleanup/optimization | Status: closed
Component: contrib.auth | Version: 2.0
Severity: Normal | Resolution: wontfix
Keywords: related_name, | Triage Stage:
related_query_name, Abstract base | Unreviewed
classes, Model inheritance |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* status: assigned => closed
* component: Database layer (models, ORM) => contrib.auth
* resolution: => wontfix
Comment:
Closing as per Simon's comments from the
[https://github.com/django/django/pull/9465 PR], "I'm afraid this is going
to break backward compatibility for every subclasses of PermissionsMixin,
default User model included. From the top of my head I can't think of any
solution that doesn't involve deprecation shims and migrations which all
seems like a lot of work. ... this is going to require a non-negligible
amount of work for something that can be worked around by using the _meta
API for the rare cases when this is an issue."
--
Ticket URL: <https://code.djangoproject.com/ticket/28931#comment:3>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.9f4f970ed68e2b6405d18a15680f7b31%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
