#35683: django.utils.timezone.make_naive can underflow for timezones close to
datetime.min
-------------------------------------+-------------------------------------
Reporter: Liam DeVoe | Owner: Shubham
| Singh Sugara
Type: Bug | Status: assigned
Component: Database layer | Version: 5.1
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham):
The use case for storing `datetime.min` and `max` is unclear, but it seems
doubtful that we should silently change the value the user provided. I
would close this ticket as "needs info" or "wontfix" unless the reporter
can provide more explanation.
--
Ticket URL: <https://code.djangoproject.com/ticket/35683#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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107019177454629-2d265207-ce66-4d7c-9468-8c03984227fc-000000%40eu-central-1.amazonses.com.
