Opened 12 years ago
Closed 12 years ago
#17883 closed Bug (fixed)
Better Error messages for 1.2 deprecations
| Reported by: | Paul McMillan | Owned by: | Jannis Leidel |
|---|---|---|---|
| Component: | Core (Other) | Version: | 1.4-beta-1 |
| Severity: | Release blocker | Keywords: | |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
As we move to 1.4 and change the required settings file format significantly, we need to provide better error messages for deprecated methods we've actually removed. In particular, both the database and cache settings provide opaque "backend not found" when a settings file uses the old style settings. This is incredibly frustrating to people who are not deeply familiar with Django settings files, or who didn't read the release notes for 1.2.
Change History (2)
comment:1 by , 12 years ago
| Component: | Uncategorized → Core (Other) |
|---|---|
| Version: | 1.3 → 1.4-beta-1 |
comment:2 by , 12 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
In [17689]: