Skip to main content
Fiddler’s Python SDKs follow a clear, predictable policy for which Python versions they support. This page explains that policy so you can plan Python upgrades with confidence.

​
Our policy

Fiddler supports each Python version through its official Python Software Foundation (PSF) end-of-life, and drops support once a version reaches PSF end-of-life. This keeps Fiddler’s SDKs aligned with Python versions that still receive upstream security patches. The PSF publishes the end-of-life date for every Python version in its Status of Python versions table — the source of truth for when a version’s support ends. Keeping your projects on a version that the PSF still supports is the most reliable way to stay on a Fiddler-supported Python. Fiddler communicates upcoming changes ahead of time so you have room to upgrade. This window — support through PSF end-of-life — is more generous than community policies such as SPEC 0 and the superseded NEP 29, which drop older Python versions sooner.

​
Which SDKs this applies to

This policy applies to all of Fiddler’s Python SDKs. Fiddler’s JavaScript and TypeScript SDKs are not affected by Python version changes.

​
How this differs from the compatibility matrix

Two references cover Python and Fiddler versions, and they answer different questions:
  • This Python version support policy describes which Python language versions Fiddler’s Python SDKs run on.
  • The compatibility matrix maps each Fiddler Python client version to the Fiddler platform versions it works with.
Use this page to choose a supported Python version, and the compatibility matrix to choose a client version that matches your Fiddler platform.