Jason, thanks for your response. An AUTH_USER_MODEL type extension mechanism is what was looking for. It's useful to know that nothing like this exists out of the box, and that forking either third-party libraries or Django itself is the clear path forward.
On Monday, October 1, 2018 at 5:31:43 AM UTC-7, Jason wrote: > > The only other alternative that comes to mind is maintaining a fork of > django itself and overwriting the specific parts of `contrib.sites` that > you need to modify. Because the third part libraries are so tightly > integrated with that bit of django and I don't think there's a method to > specify an alternative, like AUTH_USER_MODEL is available for custom user > models. > > This is a good example of how modularity in packaging for django could be > beneficial, because you could then make your own implementation of sites > and import it with the same convention as the default package > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/d0a781ce-5f44-4d64-af5b-3ae0ac71f18f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
