Things added to the calendar would often bypass the tz.store_timezone configuration (defaulted and recommended to be UTC), and rather be stored in the tz.implicit_timezone (defaulted to local timezone). Since the local timezone often does not have a valid TZ-identifier (and also, according to the RFC, any non-UTC timezone has to be specified in the icalendar objects), tests would randomly fail dependent on the timezone on the computer running the tests. Credits to github user @fauxmight for reporting.
Things added to the calendar would often bypass the
tz.store_timezoneconfiguration (defaulted and recommended to be UTC), and rather be stored in thetz.implicit_timezone(defaulted to local timezone). Since the local timezone often does not have a valid TZ-identifier (and also, according to the RFC, any non-UTC timezone has to be specified in the icalendar objects), tests would randomly fail dependent on the timezone on the computer running the tests. Credits to github user @fauxmight for reporting.Various other bugfixes