#32661: Make lack of timezone support in TimeField more explicit.
-------------------------------------+-------------------------------------
Reporter: ab-10 | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Database | Version: 3.2
layer (models, ORM) | Keywords: timezone, datetime,
Severity: Normal | datetimefield, timefield, models
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 1
UI/UX: 0 |
-------------------------------------+-------------------------------------
As tzinfo is currently dropped silently from TimeField it leads to tricky
bugs for users who expect TimeField to have consistent behaviour with
DateTimeField.
This issue suggests two changes, happy to make a PR if the community
aggrees with them:
1. Mention that TimeField drops timezone in Model field reference:
https://docs.djangoproject.com/en/3.2/ref/models/fields/#timefield
2. Throw a warning when a TimeField with tzinfo is saved (similarly as
there's a warning when a naive DateTimeField is saved).
--
Ticket URL: <https://code.djangoproject.com/ticket/32661>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/048.2387af5c404cd81a6f76555d897a43c0%40djangoproject.com.
