https://sentry.io/share/issue/33303436382e313737363032343732/
--
Ticket URL: <https://code.djangoproject.com/ticket/27451>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* stage: Unreviewed => Accepted
Old description:
> Having a naive time in DST and turning it into a STD results in an
> `AmbiuousTimeError` in `django/contrib/syndication/views.py` for
> `pubdate`, `updatedate` and possibly others.
>
> https://sentry.io/share/issue/33303436382e313737363032343732/
New description:
Having a naive time in DST and turning it into a STD results in an
`AmbiguousTimeError` in `django/contrib/syndication/views.py` for
`pubdate`, `updatedate` and possibly others.
https://sentry.io/share/issue/33303436382e313737363032343732/
--
Comment:
I'm not sure what the proper resolution is. Perhaps providing a value for
the `is_dst` argument of `make_aware()`, but what value to use?
--
Ticket URL: <https://code.djangoproject.com/ticket/27451#comment:1>
Comment (by Tobias McNulty):
I am not sure about a fix, but we did see another one of these over the
weekend during the time change:
https://sentry.io/share/issue/ea6b31e26e164a03903f499ca7f87b29/
--
Ticket URL: <https://code.djangoproject.com/ticket/27451#comment:2>
Comment (by Claude Paroz):
Replying to [comment:2 Tobias McNulty]:
> I am not sure about a fix, but we did see another one of these over the
weekend during the time change:
https://sentry.io/share/issue/ea6b31e26e164a03903f499ca7f87b29/
It looks like this one could be fixed by making item_pubdate an aware
datetime in the first place.
--
Ticket URL: <https://code.djangoproject.com/ticket/27451#comment:3>
* cc: Carlton Gibson (added)
* status: new => closed
* resolution: => invalid
* stage: Accepted => Unreviewed
Comment:
The `is_dst` argument is deprecated and will be removed in Django 5.0 (see
#32365). Closing as no longer valid.
--
Ticket URL: <https://code.djangoproject.com/ticket/27451#comment:4>