Google Calendar Python connector
Install dex-connector-google-calendar==0.1.0 alongside a compatible Dex Python SDK. The package exposes Client, generated Config and Credentials, a generated project connection with Google OAuth and Workspace delegated refresh, and operation-specific Step factories for listEvents, getEvent, createEvent, updateEvent, and queryFreeBusy. It has no Triggers.
See examples/calendar_events for a runnable Flow with the static connection name google-calendar-events-reader. The example lists a bounded event window and persists the public result. It uses the generated project connection, so the Worker reads credentials from Dex project storage and never takes a token from Flow input.
Run provider replay and the generated OAuth agreement cases with uv run pytest tests. The example integration test requires a running dexcli dev and DEX_FLOW_SERVICE_ADDRESS, and can be run with uv run pytest examples/calendar_events/integration_test.py.
Go-recorded provider fixtures and a real Dex stack with a local Google stand-in verify request and Flow behavior. Live Google consent, delegated token minting against Google, and Calendar API calls remain unverified.
1 maintainer
Metadata
1 maintainer
Release files for dex-connector-google-calendar 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| dex_connector_google_calendar-0.1.0.tar.gz | 93.4 kB | Without provenance | Details for dex_connector_google_calendar-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| dex_connector_google_calendar-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for dex_connector_google_calendar-0.1.0-py3-none-any.whl |
Total release size: 126.6 kB
Release files / dex_connector_google_calendar-0.1.0.tar.gz
| Download URL | dex_connector_google_calendar-0.1.0.tar.gz |
|---|---|
| Size | 93.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fbb2c9b0f86623238336bd785ffe7e8bbfc327120e93fc8e2de08098eb2e2cf8
|
|
BLAKE2b-256 checksum How to use checksums |
6568c43da5bbc2d1e4fb58de9c48d5bc83364fb019c44ab0a37bd1dc6116d579
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / dex_connector_google_calendar-0.1.0-py3-none-any.whl
| Download URL | dex_connector_google_calendar-0.1.0-py3-none-any.whl |
|---|---|
| Size | 33.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
755542d8a46563c4f315731e3aeab122a5e4b08605594c29ed9abaf4d16dc14d
|
|
BLAKE2b-256 checksum How to use checksums |
04380b71fdfad08b66390787605e011e27cc9236b989a3262d8ccca8d94cf970
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for dex-connector-google-calendar 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
