It's a headache thing that replace `groups in auth.models.PermissionsMixin` to `auth.Group`. because of the backward compatibility. I can not adjust some code position. I have been written some patches. But they are not enough well. I am working on it.
在 2018年9月11日星期二 UTC+8上午1:49:33，charettes写道： > > Something I would add is that while some third-party apps leverage > swappable models it is not clear how relationships between swappable models > should be dealt with. > > This is something we'd have to figure out if `auth.Group` is made > swappable as the default model user model would depend on it. > > Simon > > > Le lundi 10 septembre 2018 11:12:52 UTC-4, Tim Graham a écrit : >> >> I'm not sure. Swappable models still have some rough edges. In >> particular, switching to a swappable model after beginning a project is >> difficult and undocumented (https://code.djangoproject.com/ticket/25313). >> To overcome this, the documentation recommends starting with a custom user >> model (https://code.djangoproject.com/ticket/24370) -- I'm not sure if >> we would want to make the same recommendation for the group model as I >> suspect it wouldn't be swapped as often. >> >> I see you created a ticket to add an AUTH_GROUP_MODEL setting. >> https://code.djangoproject.com/ticket/29748 >> >> On Thursday, September 6, 2018 at 4:13:03 PM UTC-4, snhe...@gmail.com >> wrote: >>> >>> Hi Adam, >>> >>> After you reply, I make team OneToOneField to Group. Though it can >>> sovle the basic problem. it have some problem in my scene. >>> >>> My 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 I use OneToOneField, I only transfer user and team from sender >>> to receiver. It spend 2 hour. >>> >>> After I use OneToOneField. I 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 perform. So I decide to accept your suggestion >>> and contribution to django , support AUTH_GROUP_MODEL. >>> >>> I am first to contribute to django. I am getting familar with django >>> ticket now. >>> >>> 在 2018年9月2日星期日 UTC+8上午4:41:11，Adam Johnson写道： >>>> >>>> Hi damoncheng, >>>> >>>> Previous to swappable User model, the best practice was to define a >>>> secondary model with OneToOneField to User for storing auxiliary >>>> information. You could do this for Group to solve your use case now. >>>> >>>> As for the feature request, I wouldn't be against it, though I'm not >>>> really in favour of it either. I'd estimate it to be a medium-sized Django >>>> ticket. Would you be able to make the contribution? Or are you just >>>> requesting that "someone" do it? Features don't tend to get added to >>>> Django >>>> except by motivated individuals who'd like to see them there :) >>>> >>>> Thanks, >>>> >>>> Adam >>>> >>>> On Fri, 31 Aug 2018 at 23:22, 程SN <snhe...@gmail.com> wrote: >>>> >>>>> Hi everybody, >>>>> >>>>> the information is not enough for my company in >>>>> django.contrib.auth.models.Usre and django.contrib.auth.models.Group. So >>>>> I >>>>> 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 I >>>>> use django permissions. >>>>> >>>>> Firstly, I cannot use django.contrib.auth.ModelBackend directly. >>>>> >>>>> 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}) >>>>> >>>>> Why the group cannot be changed in the settings like AUTH_USER_MODEL >>>>> ? Can Djano support AUTH_GROUP_MODEL in the further release? >>>>> >>>>> So I have to custom backend that extend >>>>> django.contrib.auth.ModelBackend and modify group to my team. >>>>> >>>>> But I find the other problem in my further developing. 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 >>>>> >>>>> It's too bad. Please support AUTH_GROUP_MODEL >>>>> >>>>> ------------------------------ >>>>> Regards, >>>>> >>>>> damoncheng >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Django developers (Contributions to Django itself)" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to django-develop...@googlegroups.com. >>>>> To post to this group, send email to django-d...@googlegroups.com. >>>>> Visit this group at https://groups.google.com/group/django-developers. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/django-developers/CABeySRubsPtBiNmH1tt8hnZTPvTz-ZqXLEZ-azBK-jodV98-HQ%40mail.gmail.com >>>>> >>>>> <https://groups.google.com/d/msgid/django-developers/CABeySRubsPtBiNmH1tt8hnZTPvTz-ZqXLEZ-azBK-jodV98-HQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> >>>> -- >>>> Adam >>>> >>> -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/8d64b778-df0e-4446-8e78-9b303677f93e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
