Version 3.0 should be fully backward-compatible with version 2.x - but there are massive code changes in version 3.0, so if you're using the Python CalDAV client library in some sharp production environment, I would recommend to wait for two months before upgrading.
Highlights
- As always, lots of compatibility-tweaking. This release have probably been tested on more server implementations than any earlier version.
- "Black Style" has been replaced with ruff. This causes quite some minor changes to the code.
- Full async support -- New
AsyncDAVClientand async domain objects using a Sans-I/O architecture. The sameCalendar,Event,Todo, etc. objects work with both sync and async clients. - Experimental JMAP client -- New
caldav.jmappackage withJMAPClientandAsyncJMAPClientfor servers implementing RFC 8620 (JMAP Core) and RFC 8984 (JMAP Calendars). Note that this is experimental, and the public API may be changed in upcoming minor-releases. - Overhaul of the official API -- v3.0 comes with an improved, more pythonic and more consistent API, but aims to be fully backeward compatible. Some work has been done on the documentation, but full QA and updates will have to wait for an upcoming patch release.