[Django] #33167: Ability to access model right after it's imported

7 views
Skip to first unread message

Django

unread,
Oct 4, 2021, 7:16:23 AM10/4/21
to django-...@googlegroups.com
#33167: Ability to access model right after it's imported
-------------------------------------+-------------------------------------
Reporter: William | Owner: William
Type: New | Status: assigned
feature |
Component: Core | Version: dev
(Other) | Keywords: model, load,
Severity: Normal | INSTALLED_APPS
Triage Stage: | Has patch: 1
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
Added so models can be accessed right after it's imported. This will allow
apps to access models from apps that have a lower index number in
settings.INSTALLED_APPS. This can be used to store settings in the
database and make them easy to change from the admin for example.

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

Django

unread,
Oct 6, 2021, 6:16:35 AM10/6/21
to django-...@googlegroups.com
#33167: Ability to access model right after it's imported
-------------------------------------+-------------------------------------
Reporter: William | Owner: William
Type: New feature | Status: closed
Component: Core (Other) | Version: dev
Severity: Normal | Resolution: wontfix
Keywords: model, load, | Triage Stage:
INSTALLED_APPS | Unreviewed
Has patch: 1 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):

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


Comment:

Hi William.

Thanks for the input. This would be a significant change in Django's
behaviour. As such it would need discussion and agreement reached prior to
proceeding. The appropriate place for that discussion would be the
DevelopersMailingList.

However, there's recent discussion on further delaying the point at which
queries are allowed that looks to hve broad backing.
https://groups.google.com/g/django-developers/c/7JwWatLfP44

As such it's unlikely that there'd be agreement to move the other way.

I hope that makes sense.

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

Reply all
Reply to author
Forward
0 new messages