Opened 11 years ago
Last modified 8 years ago
#21719 closed Cleanup/optimization
Forbid importing models before their application configuration — at Version 2
Reported by: | Aymeric Augustin | Owned by: | nobody |
---|---|---|---|
Component: | Core (Other) | Version: | dev |
Severity: | Normal | Keywords: | app-loading really-hard |
Cc: | Triage Stage: | Accepted | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description (last modified by )
It's most likely a sane requirement, although there are significant backwards-compatibility concerns.
Change History (2)
comment:1 by , 11 years ago
comment:2 by , 11 years ago
Description: | modified (diff) |
---|
Note:
See TracTickets
for help on using tickets.
We'll have to document the usage
AppConfig.get_model
as a best practice for model retrieval inAppConfig.ready
in this case since people will naively import them in theirapps
module when they want to connect signals.