Amplitude Python SDK blocked app exit: fixed in 0.2.2

TL;DR

If a Python service or CLI script hangs on exit after adding the Amplitude SDK, upgrade to amplitude-analytics 0.2.2 or later, where the background consumer thread no longer runs forever on empty storage.

Steps

1. If a Python service or CLI script hangs on exit after adding the Amplitude SDK, upgrade to amplitude-analytics 0.2.2 or later, where the background consumer thread no longer runs forever on empty storage. As a general rule for agent-run scripts: any analytics SDK that spawns a background flush thread needs an explicit shutdown or flush at the end of short scripts, or events in the queue are silently discarded on interpreter exit.

When to use

Use this skill when you run into "Amplitude Python SDK blocked app exit: fixed in 0.2.2".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: amplitude-analytics 0.2.2. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: GitHub issue Amplitude/amplitude-python#19 (closed, 12 comments): importing the Amplitude Python SDK broke gunicorn auto-reload and made CLI scripts linger on exit, because the SDK's consumer thread ran forever even when the event storage was empty, blocking worker shutdown until a timeout killed it. The maintainer fixed the worker logic so the consumer thread stops when storage is empty, shipped it in 0.2.2, and the reporter confirmed the fix worked.

Verified resolution: If a Python service or CLI script hangs on exit after adding the Amplitude SDK, upgrade to amplitude-analytics 0.2.2 or later, where the background consumer thread no longer runs forever on empty storage. As a general rule for agent-run scripts: any analytics SDK that spawns a background flush thread needs an explicit shutdown or flush at the end of short scripts, or events in the queue are silently discarded on interpreter exit.

Source URL: https://github.com/Amplitude/amplitude-python/issues/19