It is possible to create a custom Group model in Django, although there is no `settings.AUTH_GROUPS_MODEL` equivalent to `AUTH_USER_MODEL`. When creating a custom Group system one can either inherit from the Django's `Group` model, or not. If you do, you still can use `user.groups.all()`. If you do not, you need to use a different related objects manager.
The question is this: I can't seem to find anywhere in the docs where Django recommends doing it one way or another. I've always thought that a custom group should subclass Group, and that is common, but some projects apparently don't do it that way. I am asking because I am the maintainer of a reusable app that requires groups compatibility, and have come across an app that that uses a non-Django-derived groups system. Are there any best practices on this question in the Django docs or elsewhere? Thanks, Scot -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/b54c91b9-debe-4a2b-99fa-f982637568a2n%40googlegroups.com.
