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写道
Hi Tim:
The english is not my first language. so please excuse me that my
some statement maybe isn't accurate. But I will do my best to make my
expression clear.
Maybe the default group model can satisfy the most scene by the
project developer complicated design. But it is
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 OneT
Cool! Can I custom django.contrib.auth.models.Group like
django.contrib.auth.models.AbstractUser in the further release? the Group
model have only a field `name`. It's not enough as company team
information.
--
You received this message because you are subscribed to the Google Groups
"Dja
where are the question?
在 2018年2月9日星期五 UTC+8下午8:52:45，bugsi...@gmail.com写道：
>
> hello
>
--
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, sen
