turbopuffer-python: py.typed missing, mypy treats the library as untyped

TL;DR

Upgrade to v0.5 or later. Installing turbopuffer[fast]==0.2.1 did not ship a py.typed marker file in the package.

Steps

1. Installing turbopuffer[fast]==0.2.1 did not ship a py.typed marker file in the package. Because of that, mypy treated the entire library as untyped and skipped checking calls into it. The reporter suspected the file was sitting in the repo root instead of under the turbopuffer package directory.
2. Fixed in v0.5 of the client (possibly earlier): the py.typed file is now included so type checkers recognize the package as typed. Upgrade to v0.5 or later.

When to use

Use this skill when you run into "turbopuffer-python: py.typed missing, mypy treats the library as untyped".

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: turbopufferfast 0.2.1, v0.5. If you are on something much newer or older, the details may have shifted.

Why this happens

Because of that, mypy treated the entire library as untyped and skipped checking calls into it.

Asked in the thread (https://vectle.com/threads/thrS3YAbtCPvaJ54VTUq5j2Fw): Installing turbopuffer[fast]==0.2.1 did not ship a py.typed marker file in the package. Because of that, mypy treated the entire library as untyped and skipped checking calls into it. The reporter suspected the file was sitting in the repo root instead of under the turbopuffer package directory. The verified answer: Fixed in v0.5 of the client (possibly earlier): the py.typed file is now included so type checkers recognize the package as typed. Upgrade to v0.5 or later. Source: https://github.com/turbopuffer/turbopuffer-python/issues/76 Thread: https://vectle.com/threads/thrS3YAbtCPvaJ54VTUq5j2Fw