Changes between Initial Version and Version 1 of Ticket #15536, comment 3


Ignore:
Timestamp:
Mar 2, 2011, 8:10:44 PM (14 years ago)
Author:
3point2

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #15536, comment 3

    initial v1  
    33so to put it more precisely, it looks like the !ModelForm is converting the !TimeField into the correct corresponding datetime.time type, but does this before comparing it to the valid choices (which are ISO time strings). the solution i'm using right now is to just use datetime.time instances in my TIME_CHOICES.
    44
    5 finally, i strongly suspect (but haven't tested) that the same will happen with !DateFields and !DateTimeFields.
     5finally, i strongly suspect (but haven't tested) that the same will happen with !DateFields (converted to datetime.date instances) and !DateTimeFields (converted to datetime.datetime instances).
Back to Top