Tags: python-caldav/caldav
Tags
v2.2 - compatibility workarounds and misc Highlights: * New ways to set up client connections: - For cloud-based services, it should suffice to pass username, password and the name of the service, no URL needed (though, just some few providers supported so far) - If the username is in email format, then it's generally not needed to pass a URL. * v2.2 comes with lots of workarounds around lack of feature support in the servers - notably the sync-token API will work also towards servers not supporting sync-tokens. In some cases lack of server functionality is detected, but as for now it may be needed to specify what server one is user through the `features` configuration flag. * v2.2 supports more complex searches. Client-side filtering will be utilized for the things that aren't supported on the server side. 2.2.1 is released with requests support (mispelled riquests in 2.2.0), 2.2.2 with niquests support
v2.2 - compatibility work and misc Highlights: * New ways to set up client connections: - For cloud-based services, it should suffice to pass username, password and the name of the service, no URL needed (though, just some few providers supported so far) - If the username is in email format, then it's generally not needed to pass a URL. * v2.2 comes with lots of workarounds around lack of feature support in the servers - notably the sync-token API will work also towards servers not supporting sync-tokens. In some cases lack of server functionality is detected, but as for now it may be needed to specify what server one is user through the `features` configuration flag. * v2.2 supports more complex searches. Client-side filtering will be utilized for the things that aren't supported on the server side. v2.2.1 comes with request dependency, v2.2.2 comes with niquests dependency (and v2.2.0 comes with misspelled riquests dependency)
v2.2 - compatibility work and misc Highlights: * New ways to set up client connections: - For cloud-based services, it should suffice to pass username, password and the name of the service, no URL needed (though, just some few providers supported so far) - If the username is in email format, then it's generally not needed to pass a URL. * v2.2 comes with lots of workarounds around lack of feature support in the servers - notably the sync-token API will work also towards servers not supporting sync-tokens. In some cases lack of server functionality is detected, but as for now it may be needed to specify what server one is user through the `features` configuration flag. * v2.2 supports more complex searches. Client-side filtering will be utilized for the things that aren't supported on the server side. v2.2.1 comes with request dependency, v2.2.2 comes with niquests dependency (and v2.2.0 comes with misspelled riquests dependency)
v2.2 - compatibility work and misc Highlights: * New ways to set up client connections: - For cloud-based services, it should suffice to pass username, password and the name of the service, no URL needed (though, just some few providers supported so far) - If the username is in email format, then it's generally not needed to pass a URL. * v2.2 comes with lots of workarounds around lack of feature support in the servers - notably the sync-token API will work also towards servers not supporting sync-tokens. In some cases lack of server functionality is detected, but as for now it may be needed to specify what server one is user through the `features` configuration flag. * v2.2 supports more complex searches. Client-side filtering will be utilized for the things that aren't supported on the server side. v2.2.0 comes with the requests dependency, v2.2.1 comes with niquests dependency
Version 2.1.0 comes without niquests in the dependency file. Version … …2.1.2 come with niquests in the dependency file. Also fixed up some minor mistakes in the CHANGELOG. Version 2.1.1 was yet another mistake done during the release process and should be ignored.
PreviousNext