Next Python SDK major

[sentrivana]

We're preparing our next major on this branch.

The project is tracked in Linear. If you don't have access, we'll try to tag issues belonging to the project with the SDK 3.0 label on GitHub so that you can follow along.

Notable changes

• Transaction-based tracing will be removed. Span streaming will be the default tracing model.
• Python 3.6 support will be removed.

Context

You might have read this announcement about us discontinuing work on a 3.0. This is referring to the work done on the potel-base branch, which included two types of changes: a huge refactor of our tracing code on the one hand, and various unrelated changes, improvements and fixes on the other. We're dropping the huge refactor part, and only porting the rest, to a new branch and eventually a new 3.0 release.

Changes

• feat: Turn unraisable exception integration on by default #5044
• chore: Drop 3.6 from CI #5036

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.76%. Comparing base (14aff96) to head (d864ba0).
⚠️ Report is 4 commits behind head on master.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@             Coverage Diff             @@
##           master    #5005       +/-   ##
===========================================
+ Coverage   70.55%   83.76%   +13.21%     
===========================================
  Files         180      180               
  Lines       18077    18080        +3     
  Branches     3008     3009        +1     
===========================================
+ Hits        12754    15145     +2391     
+ Misses       4432     1943     -2489     
- Partials      891      992      +101     

Files with missing lines	Coverage Δ
sentry_sdk/integrations/__init__.py	88.42% <100.00%> (+0.37%)	⬆️

... and 61 files with indirect coverage changes

[github-actions]

Codecov Results 📊

✅ 110309 passed | ❌ 2 failed | ⏭️ 5424 skipped | Total: 115735 | Pass Rate: 95.31% | Execution Time: 379m 48s

📊 Comparison with Base Branch

Metric	Change
Total Tests	📉 -9292
Passed Tests	📉 -7986
Failed Tests	📈 +2
Skipped Tests	📉 -1308

➕ New Tests (2)

View new tests

• test_cache_spans_templatetag[True]
  • File: tests.integrations.django.test_cache_module
  • Status: ❌ Failing
• test_continuous_profiler_auto_start_and_stop_sampled[thread]
  • File: tests.profiler.test_continuous_profiler
  • Status: ❌ Failing

❌ Failed Tests

test_cache_spans_templatetag[True]

File: tests.integrations.django.test_cache_module
Suite: py3.10-django-v5.2.17
Error: tests/integrations/django/test_cache_module.py:480: in test_cache_spans_templatetag assert not spans[0]["attributes"]["cache.hit"] E assert not True

Stack Trace

tests/integrations/django/test_cache_module.py:480: in test_cache_spans_templatetag
    assert not spans[0]["attributes"]["cache.hit"]
E   assert not True

test_continuous_profiler_auto_start_and_stop_sampled[thread]

File: tests.profiler.test_continuous_profiler
Suite: py3.7-gevent
Error: AssertionError: profiler should not be running assert 'ef390e9fb7ea49b28a1e3c47b92325d2' is None + where 'ef390e9fb7ea49b28a1e3c47b92325d2' = get_profiler_id()

Stack Trace

tests/profiler/test_continuous_profiler.py:617: in test_continuous_profiler_auto_start_and_stop_sampled
    assert get_profiler_id() is None, "profiler should not be running"
E   AssertionError: profiler should not be running
E   assert 'ef390e9fb7ea49b28a1e3c47b92325d2' is None
E    +  where 'ef390e9fb7ea49b28a1e3c47b92325d2' = get_profiler_id()

✅ Patch coverage is 90.55%. Project has 2257 uncovered lines.
✅ Project coverage is 90.55%. Comparing base (base) to head (head).

Coverage diff

@@            Coverage Diff             @@
##          main       #PR       +/-##
==========================================
+ Coverage    90.24%    90.55%    +0.31%
==========================================
  Files          193       185        -8
  Lines        25474     23880     -1594
  Branches      9378      8802      -576
==========================================
+ Hits         22988     21623     -1365
- Misses        2486      2257      -229
- Partials      1431      1370       -61

---

Generated by Codecov Action

[github-actions]

Semver Impact of This PR

⚪ None (no version bump detected)

📋 Changelog Preview

This is how your changes will appear in the changelog.
Entries from this PR are highlighted with a left border (blockquote style).

---

New Features ✨

• (logging) Separate ignore lists for events/breadcrumbs and sentry logs by sl0thentr0py in #5698

Bug Fixes 🐛

Anthropic

• Set exception info on streaming span when applicable by alexander-alderman-webb in #5683
• Patch AsyncStream.close() and AsyncMessageStream.close() to finish spans by alexander-alderman-webb in #5675
• Patch Stream.close() and MessageStream.close() to finish spans by alexander-alderman-webb in #5674

Documentation 📚

• Add note on AI PRs to CONTRIBUTING.md by sentrivana in #5696

Internal Changes 🔧

• Add -latest alias for each integration test suite by sentrivana in #5706
• Use date-based branch names for toxgen PRs by sentrivana in #5704
• 🤖 Update test matrix with new releases (03/19) by github-actions in #5703
• Add client report tests for span streaming by sentrivana in #5677

Other

• Next Python SDK major by sentrivana in #5005

• Update CHANGELOG.md by sentrivana in #5685

---

_{🤖 This preview updates automatically when you update the PR.}

[sentry-warden]

Failed ARQ task spans keep status ok under span streaming

After switching run_job to streamed spans, _capture_exception still only sets status via scope.transaction, which is always None in streaming mode—so failed task segments stay ok unless the exception happens to escape ARQ. Update _capture_exception to set scope.streamed_span.status (as Celery does) and assert error status in the failure tests.

Evidence

• This hunk makes traces.start_span(..., parent_span=None) the only task path in _sentry_run_job.
• _capture_exception still does if scope.transaction is not None: scope.transaction.set_status(...).
• In streaming mode, Scope.transaction returns None, so that status update is a no-op.
• ARQ job failures are typically handled inside Worker.run_job, so the streamed span __exit__ often never sees the exception to mark error itself.
• Celery already maps this via scope.streamed_span.status; ARQ tests assert failure events but not task-span status.

_{Identified by Warden · code-review, find-bugs · LZ3-SDG}

[sentry-warden]

Migration guide's logging example uses the removed capture_sentry_logs option

The SDK 3.x migration guide instructs users to initialize LoggingIntegration and LoguruIntegration with capture_sentry_logs=True, but both constructors reject that keyword with TypeError. Update the example to use the new level option, or omit it because level defaults to INFO.

Evidence

• LoggingIntegration.__init__ accepts level, event_level, and breadcrumb_level; it has no capture_sentry_logs parameter.
• LoguruIntegration.__init__ likewise accepts level, event_level, and formatting/breadcrumb options, but not capture_sentry_logs.
• The guide previously states that capture_sentry_logs was removed and recommends level=None to disable capture, contradicting the example in the Removed section.
• Following the example therefore raises TypeError while initializing either integration.

Also found at 1 additional location

• sentry_sdk/consts.py:1345-1345

_{Identified by Warden · code-review, find-bugs · PSD-4YZ}

[sentry-warden]

ignore_logger rename target does not match the real API

The bullet renames ignore_logger to ignore_logger_for_breadcrumbs_and_events, but the real function and the table below both use ignore_logger_for_events.

Evidence

• sentry_sdk/integrations/logging.py defines ignore_logger_for_events and unignore_logger_for_events, not ignore_logger_for_breadcrumbs_and_events.
• Integrations such as aiohttp, celery, rq, and tornado import and call ignore_logger_for_events.
• The migration table on line 57 already maps ignore_logger → ignore_logger_for_events, contradicting the bullet on line 46.

_{Identified by Warden · code-review, find-bugs · R6Q-HNJ}