Re: [Django] #29748: Add AUTH_GROUP_MODEL setting to swap the group model

[Django]

#29748: Add AUTH_GROUP_MODEL setting to swap the group model
--+
 Reporter:  damoncheng|Owner:  Csirmaz Bendegúz
 Type:  New feature   |   Status:  closed
Component:  contrib.auth  |  Version:  dev
 Severity:  Normal|   Resolution:  wontfix
 Keywords:| Triage Stage:  Unreviewed
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Natalia Bidart):

 * resolution:   => wontfix
 * stage:  Someday/Maybe => Unreviewed
 * status:  assigned => closed

Comment:

 Replying to [comment:14 Csirmaz Bendegúz]:
 > I have submitted a patch: https://github.com/django/django/pull/18053

 As said in the [https://forum.djangoproject.com/t/custom-group-model/30070
 forum post], thank you so much Csirmaz for your work on this.
 Nevertheless, following the forum and previous conversations, I'll be
 closing this as wontfix.
-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018ed40a9f06-061a190b-0b49-41c5-82a0-098b1eb7c6e1-00%40eu-central-1.amazonses.com.

Re: [Django] #29748: Add AUTH_GROUP_MODEL setting to swap the group model

[Django]

#29748: Add AUTH_GROUP_MODEL setting to swap the group model
--+---
 Reporter:  damoncheng|Owner:  csirmazbendeguz
 Type:  New feature   |   Status:  assigned
Component:  contrib.auth  |  Version:  dev
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Someday/Maybe
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+---
Changes (by csirmazbendeguz):

 * has_patch:  0 => 1
 * owner:  damoncheng => csirmazbendeguz

Comment:

 I have submitted a patch: https://github.com/django/django/pull/18053
-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018eaf6060a6-b1367203-9fb2-4ae7-83e9-98326d4a2992-00%40eu-central-1.amazonses.com.

Re: [Django] #29748: Add AUTH_GROUP_MODEL setting to swap the group model

[Django]

#29748: Add AUTH_GROUP_MODEL setting to swap the group model
--+-
 Reporter:  damoncheng|Owner:  damoncheng
 Type:  New feature   |   Status:  assigned
Component:  contrib.auth  |  Version:  dev
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Someday/Maybe
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+-
Comment (by Hossein ):

 defining AUTH_GROUP_MODEL in settings was a good solution, but apparently
 it needs some work to get prioritized.

 developers face problem when making a custom group model, as they want to
 add fields and methods to Group model

 https://stackoverflow.com/questions/2181039/how-do-i-extend-the-django-
 group-model


 Meanwhile, I suggest to make Group model get inherited from AbstractGroup.
 In this way, one can make a CustomGroup (AbstarctGroup) in their code.

 I made a PR to handel this:
 https://github.com/django/django/pull/17819
-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018d73986016-eee8872f-1117-4d09-8d3d-8919f10c81e4-00%40eu-central-1.amazonses.com.

Re: [Django] #29748: Add AUTH_GROUP_MODEL setting to swap the group model

[Django]

#29748: Add AUTH_GROUP_MODEL setting to swap the group model
--+-
 Reporter:  damoncheng|Owner:  damoncheng
 Type:  New feature   |   Status:  assigned
Component:  contrib.auth  |  Version:  dev
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Someday/Maybe
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+-
Changes (by JM Barbier):

 * cc: JM Barbier (added)


-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070182c3284a91-d694d67e-3ab4-4d49-970a-d2d9662b71b7-00%40eu-central-1.amazonses.com.

Re: [Django] #29748: Add AUTH_GROUP_MODEL setting to swap the group model

[Django]

#29748: Add AUTH_GROUP_MODEL setting to swap the group model
--+-
 Reporter:  damoncheng|Owner:  damoncheng
 Type:  New feature   |   Status:  assigned
Component:  contrib.auth  |  Version:  dev
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Someday/Maybe
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+-

Comment (by Vasanth):

 Replying to [comment:4 Bernd Wechner]:

 > It's probably one evenings work for me one day after the kids are in bed
 by time I've merged in the latest master, designed and implemented the
 best patch I can imagine and then crafted a PR with description and
 reference to this ticket.

 Hello there Bernd. If you have a branch or repo with changes feel free to
 share it here. I'll help with finishing up the PR as much as I can to get
 this ticket into prod within the next couple of releases.

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018291f0f47b-4428481b-6d25-4df7-b6cd-f5dc8034d1d4-00%40eu-central-1.amazonses.com.

Re: [Django] #29748: Add AUTH_GROUP_MODEL setting to swap the group model

[Django]

#29748: Add AUTH_GROUP_MODEL setting to swap the group model
--+-
 Reporter:  damoncheng|Owner:  damoncheng
 Type:  New feature   |   Status:  assigned
Component:  contrib.auth  |  Version:  dev
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Someday/Maybe
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+-

Comment (by Michael):

 > So it's not **nothing** but it is rather trivial all the same, and I'm
 very to code it up, run the tests, PR it. But don't want to waste my time
 if it's not welcome. I could infer it's welcome from the triage three
 years ago to **Someday / Maybe**. But will fish here for some
 encouragement first.

 Please submit the PR, I think this feature will add a lot of benefit to
 people who are in the same boat.

 Just this single post on customizing django group has 11K views:
 https://stackoverflow.com/questions/33068424/customize-django-group-model

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070181b5d1fa78-c4d66f0a-4f88-4a22-81b1-eee60a23dd0c-00%40eu-central-1.amazonses.com.

Re: [Django] #29748: Add AUTH_GROUP_MODEL setting to swap the group model

[Django]

#29748: Add AUTH_GROUP_MODEL setting to swap the group model
--+-
 Reporter:  damoncheng|Owner:  damoncheng
 Type:  New feature   |   Status:  assigned
Component:  contrib.auth  |  Version:  dev
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Someday/Maybe
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+-

Comment (by Michael):

 I was just about to open ticket for this exact same thing. The most common
 use case I have come across when searching for a solution is to add a
 `description` field to the `Group` model. There seems to be no
 complicated/hacky solution to this. Most solution end up creating custom
 migrations within:

 {{{
 site-packages/django/contrib/auth/migrations/
 }}}

 Which lives outside ones project, and can't be version controlled.

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070181b5c86457-296251fc-f7bf-43ae-b0a0-f0a4a394c461-00%40eu-central-1.amazonses.com.

Re: [Django] #29748: Add AUTH_GROUP_MODEL setting to swap the group model

[Django]

#29748: Add AUTH_GROUP_MODEL setting to swap the group model
--+-
 Reporter:  damoncheng|Owner:  damoncheng
 Type:  New feature   |   Status:  assigned
Component:  contrib.auth  |  Version:  dev
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Someday/Maybe
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+-
Description changed by Michael:

Old description:

> I was just about to open ticket for this exact same thing. The most
> common use case I have come across when searching for a solution is to
> add a `description` field to the `Group` model. There seems to be no
> complicated/hacky solution to this. Most solution end up creating custom
> migrations within:
>
> {{{
> site-packages/django/contrib/auth/migrations/
> }}}
>
> Which lives outside ones project, and can't be version controlled.

New description:

 The information is not enough for the most project in
 django.contrib.auth.models.User and django.contrib.auth.models.Group. The
 project can only custom User and Team model.

 The auth User can be changed in the django settings by AUTH_USER_MODEL.
 But the Group cannot.

 Further, There are many group permissions problem presented when project
 use django permissions.

 Firstly, In django.contrib.auth.ModelBackend,  Django currently bind group
 permissions with django.contrib.auth.models.Group


 {{{
 def _get_group_permissions(self, user_obj):
 user_groups_field = get_user_model()._meta.get_field('groups')
 user_groups_query = 'group__%s' %
 user_groups_field.related_query_name()
 return Permission.objects.filter(**{user_groups_query: user_obj})
 }}}


 If the project want to relate the group permission to custom team. the
 project have to custom backend that extend
 django.contrib.auth.ModelBackend and modify group to team.

 Secondly,  the bad design limit the other app design,  many app about
 django permission , only  support group permission based on
 django.contrib.auth.models.Group, like django-guardian.

 In the conversation with  Adam
 Johnson([https://groups.google.com/forum/#!topic/django-
 developers/llQJZUKejXg]).  Admin suggestion me to contribute it or to use
 OneToOneField to solve the basic problem. But the OneToOneField is not
 elegant and it have problem in  some scene. For example,  A project is a
 cloud item,  It use SCIM to manage user and team  identities in cloud.  it
 transfer resource from sender to many receiver.

 Before the  project use OneToOneField,   The project  only transfer user
 and team from sender to receiver.   It spend 2 hour.

 After the project use OneToOneField.  The project need transfer user and
 team from sender to receiver,  then create group and make team
 OneToOneField to Group in the receiver. It spend 6 hour.

 it degrade the transform performence.

 So please make me to support AUTH_GROUP_MODEL  that optimize django group
 permission design

--

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070181b5c68266-bf67a012-7d33-44f9-be52-149956dff9b8-00%40eu-central-1.amazonses.com.

Re: [Django] #29748: Add AUTH_GROUP_MODEL setting to swap the group model

[Django]

#29748: Add AUTH_GROUP_MODEL setting to swap the group model
--+-
 Reporter:  damoncheng|Owner:  damoncheng
 Type:  New feature   |   Status:  assigned
Component:  contrib.auth  |  Version:  dev
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Someday/Maybe
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+-
Description changed by Michael:

Old description:

> The information is not enough for the most project in
> django.contrib.auth.models.User and django.contrib.auth.models.Group. The
> project can only custom User and Team model.
>
> The auth User can be changed in the django settings by AUTH_USER_MODEL.
> But the Group cannot.
>
> Further, There are many group permissions problem presented when project
> use django permissions.
>
> Firstly, In django.contrib.auth.ModelBackend,  Django currently bind
> group permissions with django.contrib.auth.models.Group
>

> {{{
> def _get_group_permissions(self, user_obj):
> user_groups_field = get_user_model()._meta.get_field('groups')
> user_groups_query = 'group__%s' %
> user_groups_field.related_query_name()
> return Permission.objects.filter(**{user_groups_query: user_obj})
> }}}
>

> If the project want to relate the group permission to custom team. the
> project have to custom backend that extend
> django.contrib.auth.ModelBackend and modify group to team.
>
> Secondly,  the bad design limit the other app design,  many app about
> django permission , only  support group permission based on
> django.contrib.auth.models.Group, like django-guardian.
>
> In the conversation with  Adam
> Johnson([https://groups.google.com/forum/#!topic/django-
> developers/llQJZUKejXg]).  Admin suggestion me to contribute it or to use
> OneToOneField to solve the basic problem. But the OneToOneField is not
> elegant and it have problem in  some scene. For example,  A project is a
> cloud item,  It use SCIM to manage user and team  identities in cloud.
> it transfer resource from sender to many receiver.
>
> Before the  project use OneToOneField,   The project  only transfer user
> and team from sender to receiver.   It spend 2 hour.
>
> After the project use OneToOneField.  The project need transfer user and
> team from sender to receiver,  then create group and make team
> OneToOneField to Group in the receiver. It spend 6 hour.
>
> it degrade the transform performence.
>
> So please make me to support AUTH_GROUP_MODEL  that optimize django group
> permission design

New description:

 I was just about to open ticket for this exact same thing. The most common
 use case I have come across when searching for a solution is to add a
 `description` field to the `Group` model. There seems to be no
 complicated/hacky solution to this. Most solution end up creating custom
 migrations within:

 {{{
 site-packages/django/contrib/auth/migrations/
 }}}

 Which lives outside ones project, and can't be version controlled.

--

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070181b5c3740d-842b8bb7-defe-4c58-a72f-9d58aad6526c-00%40eu-central-1.amazonses.com.

Re: [Django] #29748: Add AUTH_GROUP_MODEL setting to swap the group model

[Django]

#29748: Add AUTH_GROUP_MODEL setting to swap the group model
--+-
 Reporter:  damoncheng|Owner:  damoncheng
 Type:  New feature   |   Status:  assigned
Component:  contrib.auth  |  Version:  dev
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Someday/Maybe
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+-

Comment (by Gian Luca Decurtins):

 Hi Bernd, do you think this could be something to be added in the upcoming
 Django 4.1 release?

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/010701814204d288-a37e9be5-c489-4f11-8d5f-a9b2eaad0f50-00%40eu-central-1.amazonses.com.

Re: [Django] #29748: Add AUTH_GROUP_MODEL setting to swap the group model

[Django]

#29748: Add AUTH_GROUP_MODEL setting to swap the group model
--+-
 Reporter:  damoncheng|Owner:  damoncheng
 Type:  New feature   |   Status:  assigned
Component:  contrib.auth  |  Version:  dev
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Someday/Maybe
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+-

Comment (by Gian Luca Decurtins):

 Who will take a decision on the PR? Is there anyone I could try to reach
 out to?

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070180bd30ae11-24e153e5-7a8b-47f2-99c9-f08fc8a1e96f-00%40eu-central-1.amazonses.com.

Re: [Django] #29748: Add AUTH_GROUP_MODEL setting to swap the group model

[Django]

#29748: Add AUTH_GROUP_MODEL setting to swap the group model
--+-
 Reporter:  damoncheng|Owner:  damoncheng
 Type:  New feature   |   Status:  assigned
Component:  contrib.auth  |  Version:  dev
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Someday/Maybe
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+-

Comment (by Bernd Wechner):

 > Definitely interested in such a feature - in my current project I now
 face a similar challenge. Create a Team model with a OneToOne field or
 wait for some elegant solution. Sadly I can't contribute to this one as I
 think this area is too risky for a beginner.

 I'm happy to implement it and PR it. It's not a biggie. Just a waste of
 time if the PR is likely to bounce for unforeseen reasons, that is the
 whole idea meets with opposition at the triage level. Given this ticket
 exists and isn't closed as "won't do" that is a positive sign and your
 interest contributes to that, meaning I might risk doing it some time
 ;-).. It's probably one evenings work for me one day after the kids are in
 bed by time I've merged in the latest master, designed and implemented the
 best patch I can imagine and then crafted a PR with description and
 reference to this ticket.

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.d57ddd8708413b3c0c75e17d16563d2d%40djangoproject.com.

Re: [Django] #29748: Add AUTH_GROUP_MODEL setting to swap the group model

[Django]

#29748: Add AUTH_GROUP_MODEL setting to swap the group model
--+-
 Reporter:  damoncheng|Owner:  damoncheng
 Type:  New feature   |   Status:  assigned
Component:  contrib.auth  |  Version:  dev
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Someday/Maybe
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+-

Comment (by gldecurtins):

 Replying to [comment:2 Bernd Wechner]:
 >
 > So it's not **nothing** but it is rather trivial all the same, and I'm
 very to code it up, run the tests, PR it. But don't want to waste my time
 if it's not welcome. I could infer it's welcome from the triage three
 years ago to **Someday / Maybe**. But will fish here for some
 encouragement first.
 >
 >

 Definitely interested in such a feature - in my current project I now face
 a similar challenge. Create a Team model with a OneToOne field or wait for
 some elegant solution. Sadly I can't contribute to this one as I think
 this area is too risky for a beginner.

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.bf2f4d1606a4d6d77a3516db564d98a0%40djangoproject.com.

Re: [Django] #29748: Add AUTH_GROUP_MODEL setting to swap the group model

[Django]

#29748: Add AUTH_GROUP_MODEL setting to swap the group model
--+-
 Reporter:  damoncheng|Owner:  damoncheng
 Type:  New feature   |   Status:  assigned
Component:  contrib.auth  |  Version:  dev
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Someday/Maybe
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+-

Comment (by Bernd Wechner):

 See: https://github.com/shacker/django-todo/pull/130

 If Django core developers express a willingness to see this coded, I'm
 willing to code it up and submit a PR.

 It's not hard and is needed for consistency with the
 {{{settings.AUTH_USER_MODEL}}} setting.

 It's not 100$ trivial as it means we'd need to add not only add:


 {{{
 def get_group_model():
 """
 Return the Group model that is active in this project.
 """
 try:
 return django_apps.get_model(settings.AUTH_GROUP_MODEL,
 require_ready=False)
 except ValueError:
 raise ImproperlyConfigured("AUTH_GROUP_MODEL must be of the form
 'app_label.model_name'")
 except LookupError:
 raise ImproperlyConfigured(
 "AUTH_GROUP_MODEL refers to model '%s' that has not been
 installed" % settings.AUTH_GROUP_MODEL
 )
 }}}

 around about here:

 
https://github.com/django/django/blob/4ff500f2948bfc332b3f4159021cad06e91943d3/django/contrib/auth/__init__.py#L155

 but also we confront the fact that with configurable USER and GROUP models
 the relation between them is also perforce, configurable. We need only
 know that one exists (and can stipulate that it is to-many from USER to
 GROUP (by definition), and thus implement:

 {{{
 def user_group_field():
 find a field in get_user_model() that is a 2many relation to
 get_group_model() and return it
 }}}

 from that field the reverse field can also be fetched and we need:

 {{{
 def group_user_field():
 return the related_name for user_group_field()
 }}}


 So it's not **nothing** but it is rather trivial all the same, and I'm
 very to code it up, run the tests, PR it. But don't want to waste my time
 if it's not welcome. I could infer it's welcome from the triage three
 years ago to **Someday / Maybe**. But will fish here for some
 encouragement first.

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.f038c94dec9d35a3b856cfb497e59171%40djangoproject.com.

Re: [Django] #29748: Add AUTH_GROUP_MODEL setting to swap the group model (was: Support AUTH_GROUP_MODEL to optimize django group permission design)

[Django]

#29748: Add AUTH_GROUP_MODEL setting to swap the group model
--+-
 Reporter:  damoncheng|Owner:  damoncheng
 Type:  New feature   |   Status:  assigned
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Someday/Maybe
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+-
Changes (by Tim Graham):

 * has_patch:  1 => 0
 * stage:  Unreviewed => Someday/Maybe


Comment:

 It's unclear if the complexity is too much to implement this. See
 [https://groups.google.com/d/topic/django-
 developers/llQJZUKejXg/discussion django-developers] for the discussion.

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.9c1b7742970e0abb609bdc2dab41b608%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.