CharField fails on CharField('')
Bug #391483 reported by
Juho Vepsäläinen
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Phatch |
Fix Released
|
Low
|
Stani | ||
Bug Description
If you happen to provide '' as the default value for CharField it causes nasty user interface corruption. Perhaps it's better to have it to handle it some other way? Furthermore it would be nice if CharField() would work by default as passing ' ' as default value seems redundant.
Revision history for this message
| Stani (stani) wrote | #1 |
| Changed in phatch: | |
| assignee: | nobody → stani (stani) |
| status: | New → Confirmed |
| importance: | Undecided → Low |
Revision history for this message
| Stani (stani) wrote | #2 |
| Changed in phatch: | |
| status: | Confirmed → Fix Committed |
| Changed in phatch: | |
| milestone: | none → 0.2.1 |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Gettext crashes on '' as it provides then the full translator table.
For CharField I did not want to provide a default value by design, as mostly for every action a value is required. Eg what is the sense of the text action when there is no text provided by default? So I see see it as a validation for the ui. Mostly an empty charfield means that something is wrong. Default values should only be for the majority of the cases.