#33272: Non-installed model error isn't raised if the module is in the
submodule of
an installed app
-------------------------------------+-------------------------------------
Reporter: David Seddon | Owner: nobody
Type: Uncategorized | Status: closed
Component: Database layer | Version: 3.2
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Carlton Gibson):
Hey David.
Perhaps you could propose a change that addresses your issue? When
thinking about this yesterday, one consideration is that folks may be
[https://docs.djangoproject.com/en/3.2/topics/db/models/#organizing-
models-in-a-package organising their models as a package], so that would
need to be correctly handled. These things are often easier to consider
with a test case and change in hand, especially if small.
--
Ticket URL: <https://code.djangoproject.com/ticket/33272#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.52dc730fe85e194e5f4993c6c62b0177%40djangoproject.com.
