[Django] #21698: Provide a way to unregister a given model from AppConfig

[Django]

#21698: Provide a way to unregister a given model from AppConfig
------------------------------+-------------------------
Reporter: mitar | Owner: nobody
Type: New feature | Status: new
Component: Core (Other) | Version: 1.6
Severity: Normal | Keywords: app-loading
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
------------------------------+-------------------------
Provide a way to unregister a given model from AppConfig.

--
Ticket URL: <https://code.djangoproject.com/ticket/21698>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

[Django]

#21698: Provide a way to unregister a given model from AppConfig

------------------------------+--------------------------------------

Reporter: mitar | Owner: nobody
Type: New feature | Status: new
Component: Core (Other) | Version: 1.6

Severity: Normal | Resolution:

Keywords: app-loading | Triage Stage: Unreviewed

Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0

Easy pickings: 0 | UI/UX: 0

------------------------------+--------------------------------------
Changes (by aaugustin):

* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0

Comment:

The fact that models are registered is a private implementation detail
that isn't described anywhere in the documentation.

What would be the intended effect of public APIs?

--
Ticket URL: <https://code.djangoproject.com/ticket/21698#comment:1>

[Django]

#21698: Provide a way to unregister a given model from AppConfig

------------------------------+--------------------------------------

Reporter: mitar | Owner: nobody
Type: New feature | Status: new
Component: Core (Other) | Version: 1.6

Severity: Normal | Resolution:

Keywords: app-loading | Triage Stage: Unreviewed

Has patch: 0 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0

Easy pickings: 0 | UI/UX: 0

------------------------------+--------------------------------------

Comment (by mitar):

This is related in some way to #21699. So there are two ways to allow
making custom subclasses of models which should not be registered. One is
to somehow allow some configuration in `Meta` (#21682), another is to call
current metaclass which adds it, but be able to remove it from registry
immediately afterwards (a bad side-effect is that registration signal has
been already made).

--
Ticket URL: <https://code.djangoproject.com/ticket/21698#comment:2>

[Django]

#21698: Provide a way to unregister a given model from AppConfig

------------------------------+--------------------------------------
Reporter: mitar | Owner: nobody
Type: New feature | Status: closed

Component: Core (Other) | Version: 1.6

Severity: Normal | Resolution: wontfix

Keywords: app-loading | Triage Stage: Unreviewed

Has patch: 0 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0

Easy pickings: 0 | UI/UX: 0

------------------------------+--------------------------------------
Changes (by aaugustin):

* status: new => closed
* resolution: => wontfix

Comment:

Let's keep the discussion in #21699 -- I'd rather not split it across two
tickets.

The provisional answer to this particular request is "there's no public
API to register or unregister models with the app registry".

--
Ticket URL: <https://code.djangoproject.com/ticket/21698#comment:3>