You can simply register your check inside the AppConfig.ready() of some suitable app

Unfortunately, there isn't. This is a long standing problem, and one that the app-refactor was looking into; however, that effort hasn't come to fruition

Since this signal is sent during the app registry population process, and AppConfig.ready() runs after the app registry is fully populated, receivers cannot be connected in that method. One possibility is to connect them AppConfig.__init__() instead, taking care not to import models or trigger calls to the app registry.

The easiest thing is to queue the email messages and then have them sent by a daemon. Check out django-mailer.

In Python, you will find different names which start and end with the double underscore. They are called as magic methods or dunder methods.

They allow customization of class instantiation.

In Python, there are at least a couple other ways in which effectively the same thing can be accomplished

You can use Q objects to achieve this.

Currently Django models only support a single column in this set, denying many designs where the natural primary key of a table is multiple columns.

I hit upon the idea of using Django’s Proxy models, and using the related Application to determine the subclass

Instead of getting the subclass of AppConfig, that we probably want to use because the business logic hangs off that, we instead get the actual AppConfig instances

Python is a dynamic language, so we should be able to do better.

7 View upvote and downvote totals. This answer is not useful Save this answer. Show activity on this post. An excellent django-annoying plugin solves this for you with AutoOneToOneField

The most common way to accomplish this is to use the Django signals system.

Instead of subclassing groups, I recommend adding a GroupType model that will have a many to many relation to group.