RRULE with UNTIL not working since version 3.9.2?

[mlorant]

I was updating an old requirements.txt file, still using icalendar==3.9.0. I decided to update to the last version. However an unit test broke. After some bisect, it seems the regression is appearing at 3.9.2. The following event is not parsed the same way than before:

BEGIN:VEVENT
UID:example-2
SUMMARY:Daily rehearsal
DESCRIPTION:Everday of the first week
DTSTART;TZID=Europe/Berlin:20150101T100000
DTEND;TZID=Europe/Berlin:20150101T120000
RRULE:FREQ=DAILY;UNTIL=20150107T10000Z
SEQUENCE:0
END:VEVENT

Here's two executions of my tests, where example-1 is a similar event with RRULE:FREQ=WEEKLY;BYDAY=MO as rrule. The test simply walk through vevents in a calendar file and prints event.get('RRULE')

$ pip install icalendar==3.9.2                       ####### First try, broken version
[...]
Successfully installed icalendar-3.9.2
$ python manage.py test [...]

example-1
vRecur({'FREQ': ['WEEKLY'], 'BYDAY': ['MO']})
-----------
example-2
None

$ pip install icalendar==3.9.1                       ####### Second try
[...]
Successfully installed icalendar-3.9.1
$ python manage.py test [...]

example-1
vRecur({'FREQ': ['WEEKLY'], 'BYDAY': ['MO']})
-----------
example-2
vRecur({'FREQ': ['DAILY'], 'UNTIL': [datetime.date(2015, 1, 7)]})

The problem is still present with icalendar=4.0.4. The RRULE is valid according to RFC5545.

[simon-budig]

I'm sorry but I missed that this is not about timezone definitions. I've deleted my misleading comments. My problem is tracked in issue #303.

[mlorant]

Apologies, I've found since then that my test fixture had a typo, and that a zero was missing in the time part:

RRULE:FREQ=DAILY;UNTIL=20150107T10000Z
                                HHmms!

With a valid format with 6 numbers after the T, it works just fine as before. In fact, the 3.9.2 silently reject invalid date-time that was validated before, but I don't think it's really a problem in that way. I'm closing the issue.

[niccokunzmann]

Thanks for reporting back!