Opened 15 years ago
Closed 11 years ago
#13205 closed Bug (wontfix)
Fix empty value detection in DateTimeField with SplitDateTimeWidget rendering
Reported by: | Owned by: | nobody | |
---|---|---|---|
Component: | Forms | Version: | 1.1 |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Accepted | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | yes |
Easy pickings: | no | UI/UX: | no |
Description
Hi,
when using a SplitDateTimeWidget for rendering, the empty value is [None, None].
I think this should be detected as an empty value.
Attached is a patch against the current Django 1.1 branch with test.
Regards, Bastian
Attachments (1)
Change History (8)
by , 15 years ago
Attachment: | django-empty-datetimefield.patch added |
---|
comment:1 by , 15 years ago
Triage Stage: | Unreviewed → Accepted |
---|
comment:2 by , 14 years ago
comment:3 by , 14 years ago
Type: | → Bug |
---|
comment:4 by , 14 years ago
Severity: | → Normal |
---|
comment:5 by , 13 years ago
Easy pickings: | unset |
---|---|
Patch needs improvement: | set |
django-empty-datetimefield.patch fails to apply cleanly on to trunk
comment:7 by , 11 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
As stated in #8898, SplitDateTimeWidget
should be used with SplitDateTimeField
. The support for SplitDateTimeWidget
in DateTimeField
will be deprecated.
Note:
See TracTickets
for help on using tickets.
Is this different from #8898?