#8242 closed (fixed)
INSTALLED_APPS with "foo.*" not populated consistently
| Reported by: | Jeremy Dunck | Owned by: | Jacob |
|---|---|---|---|
| Component: | Core (Other) | Version: | dev |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Accepted | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
On different filesystems, but using the same list of INSTALLED_APPS, the final populated list of INSTALLED_APPS can vary.
os.listdir's return list is arbitrary, so that the apps are loaded differently.
The most obvious display of this issue is where foo.* apps are listed in the admin index. However, applications might also expect to be initialized in a stable order, and Django's globbing currently fails at that.
I think simply sorting the results of listdir would address this.
Obviously, providing consistent tests for this is difficult, but I have observed it in the wild.
Attachments (1)
Change History (4)
by , 17 years ago
| Attachment: | INSTALLED_APPS-order.diff added |
|---|
comment:1 by , 17 years ago
| milestone: | post-1.0 → 1.0 |
|---|---|
| Owner: | changed from to |
| Status: | new → assigned |
| Triage Stage: | Unreviewed → Accepted |
comment:2 by , 17 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
(In [8538]) Fixed #8242: handle
foo.*consistantly in INSTALLED_APPS.