Opened 15 years ago
Closed 13 years ago
#14451 closed New feature (wontfix)
add related_name to contrib.auth.models.User for 'groups'
| Reported by: | Tom von Schwerdtner | Owned by: | anonymous |
|---|---|---|---|
| Component: | contrib.auth | Version: | 1.2 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Design decision needed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Would allow for
from django.contrib.auth.models import Group group = Group.objects.all()[0] group.members.all()
instead of the current
group.users_set.all()
You know, nexttime someone feels like kicking backwards compatibility in the groin...
Change History (7)
comment:1 by , 15 years ago
| Triage Stage: | Unreviewed → Someday/Maybe |
|---|
comment:2 by , 15 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:3 by , 15 years ago
| Severity: | → Normal |
|---|---|
| Type: | → New feature |
comment:4 by , 15 years ago
| Component: | Uncategorized → contrib.auth |
|---|---|
| Easy pickings: | unset |
| UI/UX: | unset |
comment:5 by , 14 years ago
comment:6 by , 13 years ago
| Triage Stage: | Someday/Maybe → Design decision needed |
|---|
This can be done with a deprecation path right now if we want to. During the transition, Group.users_set would be a property raising a deprecation warning and returning members.
However I don't know if there's much value in forcing this change upon all users of Django.
comment:7 by , 13 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | assigned → closed |
Actually, I cannot convinced myself there's enough value.
Note:
See TracTickets
for help on using tickets.
Milestone 2.0 deleted