#24076: Query may fail with pytz exception
-------------------------------+------------------------------------
Reporter: lvella | Owner: nobody
Type: Bug | Status: new
Component: Documentation | Version: 1.6
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
-------------------------------+------------------------------------
Changes (by Adam Zapletal):
* cc: Adam Zapletal (added)
Comment:
I wonder if this issue can be closed with no documentation changes for the
following reasons:
1. The `__date__gte` lookup (mentioned in comment 1) and others for
`DateTimeField` have been implemented for a long time.
2. `pytz` has been removed as of Django 5.0.
3. Support for time zones has now been core to Django for almost 12 years.
4. The documentation for the lookup mentioned above seems sufficient to me
to help future users wondering how to compare a `DateTimeField` with a
`datetime.date`:
https://docs.djangoproject.com/en/dev/ref/models/querysets/#date.
However, I'd be happy to work on a documentation patch if someone can
provide an idea of what is needed to close this ticket.
--
Ticket URL: <https://code.djangoproject.com/ticket/24076#comment:4>
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/0107018e42915eb7-ae49bf1a-ed09-4809-b035-b97bfba6ac13-000000%40eu-central-1.amazonses.com.
