#12139: forms.fields.DateTimeField and TimeField so not accept stringified datetimes -------------------------------------+------------------------------------- Reporter: mattbennett | Owner: nobody Type: New feature | Status: closed Component: Forms | Version: master Severity: Normal | Resolution: duplicate Keywords: datetime, forms, | Triage Stage: Accepted datetimefield, timefield | Has patch: 1 | Needs documentation: 0 Needs tests: 1 | Patch needs improvement: 1 Easy pickings: 0 | UI/UX: 0 -------------------------------------+------------------------------------- Changes (by claudep):
* status: new => closed * resolution: => duplicate Comment: I don't think this is a problem any longer nowadays. See #9459/[dce278673a409a10c1f74f597035b737bbf6a017] and #19917 [384c180e414a982a6cc5ccabc675bcfb4fd80988] -- Ticket URL: <https://code.djangoproject.com/ticket/12139#comment:6> 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/069.01d4b6281393586956c8ca9f6d56af44%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.