The Python SDK ships as a regular wheel. Under the hood it loads telequick_core_ffi.so (Linux), .dylib (macOS), or .dll (Windows) via ctypes. The wheel bundles the right binary for your platform; if you build the SDK yourself, point TELEQUICK_LIB_PATH at the .so location.

​
Requirements

  • Python ≥ 3.10
  • A C QUIC stack — the SDK uses aioquic, pulled in as a dependency.
  • A platform cryptography build for JWT signing (pip will install one).

​
Install

pip install telequick
For local development against a checkout: 
git clone https://github.com/telequick/telequick-sdk.git
cd telequick-sdk/python
pip install -e .

# Build the native FFI:
bazel build //core:telequick_core_ffi.so
export TELEQUICK_LIB_PATH=$(pwd)/../bazel-bin/core/telequick_core_ffi.so

​
Smoke test

from telequick.client import TeleQuickClient
print(TeleQuickClient)  # should print the class object
If you see FileNotFoundError: Could not find ... FFI Core Library the SDK couldn’t locate the native lib. Either:
  1. Install the wheel from PyPI (it bundles the lib), or
  2. Set TELEQUICK_LIB_PATH to the absolute path of telequick_core_ffi.so.

​
Credentials

Drop your service-account JSON somewhere readable, then either:
  • Pass the path to TeleQuickClient(service_account_path=...) directly, or
  • Export TELEQUICK_CREDENTIALS and let the SDK pick it up.
export TELEQUICK_CREDENTIALS=/etc/telequick/service-account.json
See Authentication for the file format.