Opened 17 years ago
Closed 17 years ago
#6492 closed (fixed)
isValidFloat() should handle Unicode data
Reported by: | Owned by: | nobody | |
---|---|---|---|
Component: | Template system | Version: | dev |
Severity: | Keywords: | ||
Cc: | Triage Stage: | Ready for checkin | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
The isValidFloat() can receive Unicode data in which case str() fails.
The patch uses smart_str() to cope with this.
Attachments (2)
Change History (7)
by , 17 years ago
Attachment: | 0023-isValidFloat-should-handle-Unicode-data.patch added |
---|
comment:1 by , 17 years ago
Component: | Uncategorized → Template system |
---|
comment:2 by , 17 years ago
Needs tests: | set |
---|---|
Triage Stage: | Unreviewed → Accepted |
by , 17 years ago
Attachment: | django-isvalidfloat-test.diff added |
---|
unittest for isValidFloat() unicode fix
comment:3 by , 17 years ago
Needs tests: | unset |
---|
comment:4 by , 17 years ago
Triage Stage: | Accepted → Ready for checkin |
---|
Good good (next time, just combine the tests with the actual fix into one patch)
comment:5 by , 17 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Straight-forwards patch, but may as well have a regression test...