Problems with latest python-dateutil

[jensens]

I tried to update our Plone dependencies to python-dateutil 2.7.2 which broke, see plone/buildout.coredev#447

I found it is an icalendar issue. Also icalendar Travis CI https://travis-ci.org/collective/icalendar/builds/361592061is red.

[kyrias]

Reading RFC 5545 a bit closer it seems that the dateutil exception is misleading, and it's the test case that's wrong.

RFC 5545 ¶3.3.10

                                             Furthermore, if the
      "DTSTART" property is specified as a date with local time, then
      the UNTIL rule part MUST also be specified as a date with local
      time.  If the "DTSTART" property is specified as a date with UTC
      time or a date with local time and time zone reference, then the
      UNTIL rule part MUST be specified as a date with UTC time.  In the
      case of the "STANDARD" and "DAYLIGHT" sub-components the UNTIL
      rule part MUST always be specified as a date with UTC time.

While this is the actual test data that fails, where UNTIL is in UTC (which it has to be since it's a DAYLIGHT sub-component), but DTSTART doesn't specify the timezone so is in local time, which is invalid as per the RFC above.

[legrostdg]

What is the recommendation for this test? Should it be disabled? python-icalendar (and its reverse dependencies) will be removed from Debian testing soon (on 2018-10-24)... https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908498

[jensens]

This is solved for now, follow up see #274

[legrostdg]

Would it be possible to do a new release with this fix? This would help Debian packaging. Thanks!

[jensens]

@esteele @mauritsvanrees @thet can we have a release of the latest fixes please?

[mauritsvanrees]

There you go: https://pypi.org/project/icalendar/4.0.3/

[legrostdg]

Great, thanks!