Index | Thread | Search

From:
Stuart Henderson <stu@spacehopper.org>
Subject:
Re: [update] devel/py-icalendar 4.0.4 -> 6.3.1
To:
Johannes Thyssen Tishman <jtt@openbsd.org>, <ports@openbsd.org>
Cc:
Joerg Jung <jung@openbsd.org>
Date:
Fri, 26 Sep 2025 19:42:54 +0100

Download raw body.

Thread
maybe a day or two but if there are no big concerns it would be good to get 
in sooner so there's more opportunity to find any runtime issues.

thanks for updating this set of ports - it had been on my radar for a while 
but not got round to it - most had been unmaintained upstream for a while 
but they've been picking up pace recently :)

-- 
  Sent from a phone, apologies for poor formatting.

On 26 September 2025 19:21:16 Johannes Thyssen Tishman <jtt@openbsd.org> wrote:

> 2025-09-26T18:18:31+0100 Stuart Henderson <stu@spacehopper.org>:
>> On 2025/09/26 16:06, Johannes Thyssen Tishman wrote:
>> > Please find below an update for devel/py-icalendar to version 6.3.1.
>> >
>> > This update is needed to update productivity/py-caldav to version 2.0.1
>> > which I'll send in a bit as well. All tests are passing.
>> >
>> > Consumers build fine:
>> > 	misc/remind-caldav
>> > 	productivity/gtg
>> > 	productivity/khal
>> > 	productivity/py-caldav
>> > 	productivity/topydo
>> >
>> > I noticed some issues in productivity/{gtg,khal}, but they are
>> > unrelated:
>> >
>> > productivity/gtg:
>> >
>> > 	Runtime broken due to "ModuleNotFoundError: No module named 'imp'"
>> >
>> > productivity/khal:
>> >
>> > 	Some tests fail due to:
>> > 	"AttributeError: 'zoneinfo.ZoneInfo' object has no attribute 'localize'"
>> >
>> > 	Updating to the latest version should fix this:
>> > 	https://github.com/pimutils/khal/issues/1411
>>
>> Reviewing changelog, there's a chance of some issues from this breaking
>> change that would likely only show up at runtime,
>>
>>     "If you rely on icalendar providing timezones from pytz, you can add
>>     one line to your code to get the behavior of versions below 6:
>>
>>     import icalendar
>>     icalendar.use_pytz()"
>>
>> but I think this was done long enough ago that there are likely to be
>> fixes available if anything does show up. I'm basically OK with the
>> update. One small issue, pytz is no longer needed as a dependency so
>> can be dropped.
>
> Thanks sthen@, nice catch. Should we wait for jung@ or can this go in?