Opened 14 years ago

Closed 10 years ago

#13205 closed Bug (wontfix)

Fix empty value detection in DateTimeField with SplitDateTimeWidget rendering

Reported by: Bastian Kleineidam <calvin@…> 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



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)

django-empty-datetimefield.patch (2.0 KB ) - added by Bastian Kleineidam <calvin@…> 14 years ago.

Download all attachments as: .zip

Change History (8)

by Bastian Kleineidam <calvin@…>, 14 years ago

comment:1 by Russell Keith-Magee, 14 years ago

Triage Stage: UnreviewedAccepted

comment:2 by Karen Tracey, 14 years ago

Is this different from #8898?

comment:3 by Luke Plant, 13 years ago

Type: Bug

comment:4 by Luke Plant, 13 years ago

Severity: Normal

comment:5 by patchhammer, 13 years ago

Easy pickings: unset
Patch needs improvement: set

django-empty-datetimefield.patch fails to apply cleanly on to trunk

comment:6 by Aymeric Augustin, 12 years ago

UI/UX: unset

Change UI/UX from NULL to False.

comment:7 by Claude Paroz, 10 years ago

Resolution: wontfix
Status: newclosed

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.
Back to Top