#28090: TimeField rendering in admin forms -----------------------------------------+------------------------ Reporter: Tomek Rej | Owner: nobody Type: Bug | Status: new Component: Uncategorized | Version: 1.11 Severity: Normal | Keywords: Triage Stage: Unreviewed | Has patch: 0 Needs documentation: 0 | Needs tests: 0 Patch needs improvement: 0 | Easy pickings: 0 UI/UX: 0 | -----------------------------------------+------------------------ When passing a datetime.Time instance to the choices parameter in a TimeField, the admin template converts it to a human readable form. Eg Time(0, 0) gets converted to "midnight", Time(1, 30) gets converted to 1:30 a.m. In Django 1.10 it gets formatted as 00:00:00 and 01:30:00 respectively.
An example of the choices I pass in to the constructor is: {{{ [ (datetime.Time(0, 0), '00:00'), (datetime.Time(0, 30), '00:30'), (datetime.Time(1, 0), '01:00'), ...., (datetime.Time(23, 30), '23:30') ] }}} This causes the admin form validation to fail with errors like the following: ''Select a valid choice. midnight is not one of the available choices.'' -- Ticket URL: <https://code.djangoproject.com/ticket/28090> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "Django updates" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-updates+unsubscr...@googlegroups.com. To post to this group, send email to django-updates@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/052.411e858e9114ba5db3fc3ed60b3d0f77%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.