TZ info in dates not respected / no support of DATE values / recurring dates are not DST adjusted
Bug #890196 reported by
thet
This bug affects 4 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| dateutil |
Confirmed
|
Undecided
|
Tomi Hukkalainen | ||
Bug Description
* When doing recurring-date calculations with python-dateutil, TZ info in rrulestr is not recognized
dates over DST. see: (3)
* Date/Time components in rrulestr do not respect DATE values - thus, python-datetime cannot parse DATE only dates, just DATETIME. See: (2)
* Recurring Dates over Daylight Saving Time changes are not adjusted properly. See: (1)
(1)(2)(3) I've created some doctests with examples of these bugs. See the attached file or: https:/
Revision history for this message
| thet (thet) wrote | #1 |
| Changed in dateutil: | |
| assignee: | nobody → Tomi Pieviläinen (tpievila) |
| status: | New → Confirmed |
Revision history for this message
| Tomi Hukkalainen (tpievila) wrote | #2 |
To post a comment you must log in.
More weirdness. Example: create a weekly recurring event in Monday midnight in UTC+3. The event is actually recorded on Sunday 9PM UTC. The rrule still marks the BYWEEKDAY to Monday. If saved to ical, and loaded back, rrulestr starts counting the first occurance from Monday... UTC. Which throws the first actual event in UTC+3 over to Tuesday.
So the logic is not the same when saving and loading.