#29861: Use timezone.now() instead of datetime.now() for TimeField's
auto_now/auto_now_add
-------------------------------------+-------------------------------------
Reporter: italomg | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Database layer | Version: 2.1
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: timezone; | Triage Stage:
TimeField; DateTimeField | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* status: new => closed
* resolution: => invalid
Comment:
Unlike `DateTimeField`, `TimeField` isn't timezone-aware. See #18691 for
discussion.
--
Ticket URL: <https://code.djangoproject.com/ticket/29861#comment:1>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.5c1007322db2eeb4403ded0d1b60bb8b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
