Invalid DST boundaries/utc_transition_times

Bug #1843916 reported by Vijay Kal on 2019-09-13
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pytz
Undecided
Unassigned

Bug Description

pytz version: 2019.2
Per olson database for Israel:
# As of 2013, DST starts at 02:00 on the Friday before the last Sunday
# in March. DST ends at 02:00 on the last Sunday of October.

Israel will still be under daylight savings on Oct 9th 2019 , but pytz incorrectly identifies this date does not have any DST offset (offset = 0)

Python code to recreate:
print bool(timezone('Asia/Jerusalem').dst(datetime(2019, 10, 9), is_dst=None))

This returns False, should ahve been True

Additional Info:
I see that we have incorrect DST boundaries for various zones.
If we have invalid boundaries any check to see if a given date is in DST during this invalid period would be incorrect.

P.S. Sorry I also did ask a question (9683902) regarding this

Vijay Kal (vkalusani) wrote :

More Info:

from: https://git.launchpad.net/pytz/tree/tz/asia

Rule:

# Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S
Rule Zion 2013 max - Mar Fri>=23 2:00 1:00 D
Rule Zion 2013 max - Oct lastSun 2:00 0 S

Per this rule DST end's on last sunday of October which is October 27, but per pytz it ends on October 05, 2019.
Do we know whey we have wrong transition time reported for Asia/Jerusalem eventhough the database has correct info?

Vijay Kal (vkalusani) wrote :

Had pytz-2012c previously manually installed ..sorry for the confusion and waste of your time.
the rule came from older database which was installed with pytz-2012c
Please close this invlaid bug report

Manfred Hampl (m-hampl) on 2019-09-17
Changed in pytz:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers