SDK 2.0

[sentrivana]

Work on the next major of sentry-python is underway. Here's what's coming:

Removing support for Python 2.7 and 3.5

• Remove Support for Python 2.x #2004
• Drop support for Python 3.4 and 3.5 #1255

Security support for both Python 2.7 and 3.5 ended in 2020. We keep a lot of compatibility code and hacks around in the SDK to support Python 2. Additionally, since the ecosystem has largely moved on, a lot of our tooling is frozen at the last version that still supports Python 2.

Dropping support for these legacy Python versions will allow us to better focus on providing support for Python 3.6 and newer, as well as explore possibilities where we were previously limited by our support for EOL Python versions (for instance, better OpenTelemetry support, better typing).

SDK version 1.* isn't going anywhere and can continue to be used. It will however not receive any new features.

Sunsetting the deprecated /store endpoint

• Sun-setting the /store endpoint #1957

Support for sending events to the deprecated /store endpoint will be removed.
(If you are using an on-premise/self-hosted installation of Sentry, the minimum requirement is now version >= v20.6.0)

Hubs and scopes refactor

• Refactor Hubs & Scopes #2533

We're changing the inner workings of the SDK. The current public API (e.g. push_scope) will continue to work in SDK 2.0, but will be deprecated and scheduled for removal in the next major.

Other changes

In addition to the three biggest changes outlined above, we have a small wishlist of mostly refactoring ideas that we'll include in the major if time permits.

Plan

• The development is happening on the sentry-sdk-2.0 branch, which will eventually be merged into the main branch.
• In SDK 2.0 also the refactoring of our Hubs and Scopes is included:
  (1) Add new scopes related API (but not yet calling it) #2609
• We're planning an alpha release on PyPI end of February. This will be released from the sentry-sdk-2.0 branch.
• We're targeting mid March 2024 for the final release.