[Django] #21682: Move relevant fields from Model._meta to Model._meta.app_config
Django
-------------------------------------+-------------------------------------
Reporter: aaugustin | Owner: nobody
Type: New | Status: new
feature | Version: master
Component: Database | Keywords: app-loading
layer (models, ORM) | Has patch: 0
Severity: Normal | Needs tests: 0
Triage Stage: | Easy pickings: 0
Unreviewed |
Needs documentation: 0 |
Patch needs improvement: 0 |
UI/UX: 0 |
-------------------------------------+-------------------------------------
This is a very general idea for which I don't have a clear proposal yet.
--
Ticket URL: <https://code.djangoproject.com/ticket/21682>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
-------------------------------------+-------------------------------------
Reporter: aaugustin | Owner: nobody
Component: Database layer | Version: master
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: app-loading | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by mitar):
* cc: mmitar@… (added)
Comment:
Could here be also added that you do not want a model to be registered?
--
Ticket URL: <https://code.djangoproject.com/ticket/21682#comment:2>
Django
-------------------------------------+-------------------------------------
Reporter: aaugustin | Owner: nobody
Component: Database layer | Version: master
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: app-loading | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by aaugustin):
Well... What's the use case?
The fact that models are registered is a private implementation detail
that isn't described anywhere in the documentation.
--
Ticket URL: <https://code.djangoproject.com/ticket/21682#comment:3>
Django
-------------------------------------+-------------------------------------
Reporter: aaugustin | Owner: nobody
Component: Database layer | Version: master
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: app-loading | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by aaugustin):
In fact, the real question this ticket asks is -- should the Options class
take an app_config in argument rather than an app_label?
I'm changing the title accordingly.
We aren't guaranteed to have an app_config available as long as:
- models can live outside of installed applications (#21680)
- applications / application configurations can import models (#21719)
I'm not sure we'll make drastic choices on these two tickets.
This ticket is likely to end up as wontfix, but it's probably worth
keeping until the dust of app-loading settles (after the 1.7 release).
--
Ticket URL: <https://code.djangoproject.com/ticket/21682#comment:4>
Django
Reporter: aaugustin | Owner: nobody
Component: Database layer | Version: master
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
* keywords: app-loading => app-loading 1.9
Comment:
This ticket cannot move forward until Django 1.9.
--
Ticket URL: <https://code.djangoproject.com/ticket/21682#comment:5>
Django
Reporter: aaugustin | Owner: nobody
Component: Database layer | Version: master
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: app-loading 1.9 | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
* cc: pirosb3 (added)
--
Ticket URL: <https://code.djangoproject.com/ticket/21682#comment:6>
Django
Reporter: aaugustin | Owner: nobody
Component: Database layer | Version: master
(models, ORM) |
Keywords: app-loading 1.9 | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by aaugustin):
I took a stab at this, unfortunately, it doesn't play well with the fake
"migrations" app label declared by the Migration model.
--
Ticket URL: <https://code.djangoproject.com/ticket/21682#comment:7>
Django
Reporter: aaugustin | Owner: nobody
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
* keywords: app-loading 1.9 => app-loading
--
Ticket URL: <https://code.djangoproject.com/ticket/21682#comment:8>
Django
-------------------------------------+-------------------------------------
Type: New feature | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: app-loading | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
* Attachment "Engineering.pdf" added.
Django
-------------------------------------+-------------------------------------
Reporter: Aymeric Augustin | Owner: nobody
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: app-loading | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
* status: new => closed
* resolution: => wontfix
Comment:
Finally going to resolve this ticket as ''wontfix''. As pointed out by
Aymeric there are complications wrt/ to migration fake models and quite
frankly it's not clear to me what benefits it would provide over the rare
cases where `self.apps(self.app_label)` is used.
--
Ticket URL: <https://code.djangoproject.com/ticket/21682#comment:9>