posthog

PostHog Python

Please see the Python integration docs for details.

Python Version Support

SDK Version	Python Versions Supported	Notes
7.3.1+	3.10, 3.11, 3.12, 3.13, 3.14	Added Python 3.14 support
7.0.0 - 7.0.1	3.10, 3.11, 3.12, 3.13	Dropped Python 3.9 support
4.0.1 - 6.x	3.9, 3.10, 3.11, 3.12, 3.13	Python 3.9+ required

Development

This repo requires all commits to be signed. To configure commit signing, see the PostHog handbook.

Testing Locally

We recommend using uv. It's super fast.

• Run uv venv env (creates virtual environment called "env")
  • or python3 -m venv env
• Run source env/bin/activate (activates the virtual environment)
• Run uv sync --extra dev --extra test (installs the package in develop mode, along with test dependencies)
  • or pip install -e ".[dev,test]"
• you have to run pre-commit install to have auto linting pre commit
• Run make test
• To run a specific test do pytest -k test_no_api_key

PostHog recommends uv so...

uv python install 3.12
uv python pin 3.12
uv venv
source env/bin/activate
uv sync --extra dev --extra test
pre-commit install
make test

Running Locally

Assuming you have a local version of PostHog running, you can run python3 example.py to see the library in action.

Testing changes locally with the PostHog app

You can run make prep_local, and it'll create a new folder alongside the SDK repo one called posthog-python-local, which you can then import into the posthog project by changing pyproject.toml to look like this:

dependencies = [
    ...
    "posthoganalytics" #NOTE: no version number
    ...
]
...
[tools.uv.sources]
posthoganalytics = { path = "../posthog-python-local" }

This'll let you build and test SDK changes fully locally, incorporating them into your local posthog app stack. It mainly takes care of the posthog -> posthoganalytics module renaming. You'll need to re-run make prep_local each time you make a change, and re-run uv sync --active in the posthog app project.

Releasing

This repository uses Sampo for versioning, changelogs, and publishing to crates.io.

• When making changes, include a changeset: sampo add
• Create a PR with your changes and the changeset file
• Add the release label and merge to main
• Approve the release in Slack when prompted — this triggers version bump, crates.io publish, git tag, and GitHub Release

You can also trigger a release manually via the workflow's workflow_dispatch trigger (still requires pending changesets).