#14002 closed (fixed)
filesizeformat filter only supports up to GB
Reported by: | Aaron T. Myers | Owned by: | Aaron T. Myers |
---|---|---|---|
Component: | Template system | Version: | |
Severity: | Keywords: | ||
Cc: | Triage Stage: | Ready for checkin | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | yes | Patch needs improvement: | yes |
Easy pickings: | no | UI/UX: | no |
Description
The product that I work on routinely displays file sizes which are larger than 1 TB, some times larger than 1 PB. The filesizeformat template filter defaults to GB for anything larger than MB. I'd like filesizeformat to support larger sizes.
Attachments (2)
Change History (12)
by , 14 years ago
Attachment: | bigger-filesizeformat.diff added |
---|
comment:1 by , 14 years ago
comment:2 by , 14 years ago
Needs tests: | set |
---|---|
Patch needs improvement: | set |
Triage Stage: | Unreviewed → Accepted |
by , 14 years ago
Attachment: | bigger-filesizeformat.2.diff added |
---|
New version with tests and addressing review comment.
comment:4 by , 14 years ago
milestone: | → 1.3 |
---|---|
Patch needs improvement: | unset |
Triage Stage: | Accepted → Ready for checkin |
comment:5 by , 14 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:6 by , 14 years ago
Strictly, the fix is actually in [13584]... but trac seems to be having some trouble with that revision.
comment:7 by , 14 years ago
There is a problem with the fix, in that units are no more translated. There are missing ugettext calls in BYTE_UNITS tuple. Reopen or open new report?
comment:8 by , 14 years ago
Patch needs improvement: | set |
---|---|
Resolution: | fixed |
Status: | closed → reopened |
No need for a new ticket; I'll update the code.
comment:9 by , 14 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
2 issues. a) Needs tests, b) for the ugettext call the % operator should be *outside* the call to ugettext, not inside.