Python SDK Releases — June 2026 (detailed)#136
Open
stephanie-anderson wants to merge 2 commits into
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
ericapisani
reviewed
Jul 9, 2026
Member
There was a problem hiding this comment.
I'd remove the "MCP SDK v2 handler signature support" - the MCP v2 API is still in alpha and we don't yet have comprehensive support for this API (there are many breaking changes being rolled out over the coming month)
Edit: the changelog as it's written looks good though, it doesn't appear to be overstating our support here.
…eal dates Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Co-Authored-By: rahul <rahul.chhabria@sentry.io>
sentry-junior
Bot
force-pushed
the
sdk-releases-june-2026/python-detailed
branch
from
c952356 to
5b25807
Compare
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
Align the TL;DR with the release notes section so url.fragment is listed alongside url.full, url.query, and url.path. Co-Authored-By: rahul <rahul.chhabria@sentry.io>
rahulchhabria
left a comment
rahulchhabria
left a comment
Contributor
There was a problem hiding this comment.
Addressed review feedback:
- TL;DR now lists
url.fragmentalongside the other PII-gated URL attributes (matches the release notes section). - Left the MCP SDK v2 handler signature mention in place based on @ericapisani's follow-up that the wording looks fine as written (not overstating support).
ericapisani
approved these changes
Jul 13, 2026
ericapisani
left a comment
ericapisani
left a comment
Member
There was a problem hiding this comment.
Small polish things that I noticed, but otherwise LGTM
|
|
||
| ## TL;DR | ||
|
|
||
| - `gen_ai` spans now stream as v2 envelope items by default — prevents drops on large transactions and removes size-based AI message truncation; self-hosted users can opt out with `stream_gen_ai_spans=False`. |
Member
There was a problem hiding this comment.
Small adjustments to try and use the same language/wording as our official docs
Suggested change
| - `gen_ai` spans now stream as v2 envelope items by default — prevents drops on large transactions and removes size-based AI message truncation; self-hosted users can opt out with `stream_gen_ai_spans=False`. | |
| - `gen_ai` spans now stream as Streamed Spans by default — prevents drops on large transactions (>1000 spans) and removes size-based AI message truncation; self-hosted users can opt out with `stream_gen_ai_spans=False`. |
|
|
||
| In 2.62.0 a new `aiomysql` integration lands for async MySQL query tracing — add `AioMySQLIntegration()` to your `integrations` list to enable it. The same release adds automatic HTTPX2 support: requests made through the `httpx2` package are instrumented with no extra setup required. | ||
|
|
||
| 2.64.0 makes `gen_ai` span streaming the default. Previously AI spans were embedded inside their parent transaction and subject to the same payload size limits; with streaming they travel as independent v2 envelope items. This means they can no longer be dropped when a transaction payload grows too large, and AI message data is no longer truncated by the SDK. Self-hosted Sentry users whose instance does not yet support streamed spans should opt out via `stream_gen_ai_spans=False`. |
Member
There was a problem hiding this comment.
Suggested change
| 2.64.0 makes `gen_ai` span streaming the default. Previously AI spans were embedded inside their parent transaction and subject to the same payload size limits; with streaming they travel as independent v2 envelope items. This means they can no longer be dropped when a transaction payload grows too large, and AI message data is no longer truncated by the SDK. Self-hosted Sentry users whose instance does not yet support streamed spans should opt out via `stream_gen_ai_spans=False`. | |
| 2.64.0 makes `gen_ai` use streamed spans (v2) by default, rather than transaction-based spans (v1). Previously AI spans were embedded inside their parent transaction and subject to the same payload size limits; with streaming they travel as independent v2 envelope items. This means they can no longer be dropped when a transaction payload grows too large, and AI message data is no longer truncated by the SDK. Self-hosted Sentry users whose instance does not yet support streamed spans should opt out via `stream_gen_ai_spans=False`. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Builds on #123 with three improvements:
## What changed→## TL;DR--
View Junior Session in Sentry