[beta] local read-only tool: which lines of your Python Twitter client break when the API changes? #2243

I built a small Python-first, read-only scanner and would value tweepy maintainers' read on it.

In one command it takes a Python repo that calls a REST/OpenAPI API, plus the OLD and NEW API specs, and reports exactly which files / functions / lines will break — with a confidence score and the evidence behind it.

Why it may fit here: tweepy maps Twitter/X API endpoints through helpers and request mappers, and an upstream breaking change can silently break callers.

It runs entirely on your machine: no source upload, no account, no telemetry. It's a beta; I'm not selling anything — I just want to know if it saves investigation time when the API changes.

It's now public and self-serve — clone and run in ~2 minutes, no files needed from me:

https://github.com/sambanideepak/upstream-sentry

Pick two OpenAPI specs (old/new) of the API you depend on and a public copy of tweepy, then bash run_beta_scan.sh --repo ... --old-spec ... --new-spec ... --output ./out. Feedback goes back via a short form in the repo; stop anytime.

Thanks,
Deepak

UpstreamSentry — know what breaks before the API change reaches you.