feat: Allow integrations to define control flow exceptions

[sentrivana]

Description

Some frameworks we're integrating with use specific exception types for control flow. If we encounter them, we should not set the status of the current span to error.

Implement a global ignore list that each integration can populate with control flow exceptions known to it, so that whenever a span finishes, it has access to the list and can decide whether the exception that occurred constitutes an error or not.

Issues

• Closes Handle control flow exceptions when assigning span status #6408
• Closes https://linear.app/getsentry/issue/PY-2492

Reminders

• Please add tests to validate your changes, and lint your code using tox -e linters.
• Add GH Issue ID & Linear ID (if applicable)
• PR title should use conventional commit style (feat:, fix:, ref:, meta:)
• For external contributors: CONTRIBUTING.md, Sentry SDK development docs, Discord community

[github-actions]

Codecov Results 📊

✅ 282 passed | Total: 282 | Pass Rate: 100% | Execution Time: 45.40s

📊 Comparison with Base Branch

Metric	Change
Total Tests	—
Passed Tests	—
Failed Tests	—
Skipped Tests	—

✨ No test changes detected

All tests are passing successfully.

✅ Patch coverage is 100.00%. Project has 14769 uncovered lines.
✅ Project coverage is 34.91%. Comparing base (base) to head (head).

Files with missing lines (1)

File	Patch %	Lines
sentry_sdk/utils.py	100.00%	⚠️ 1 partials

Coverage diff

@@            Coverage Diff             @@
##          main       #PR       +/-##
==========================================
+ Coverage    34.91%    34.91%        —%
==========================================
  Files          190       190         —
  Lines        22689     22689         —
  Branches      7742      7742         —
==========================================
+ Hits          7920      7920         —
- Misses       14769     14769         —
- Partials       832       832         —

---

Generated by Codecov Action

[sentry-warden]

No tests cover the new control-flow exception mechanism

There are no tests validating that register_control_flow_exception / should_be_treated_as_error suppress span-error status for registered exceptions, nor that AioHttpIntegration correctly exempts HTTPException — please add coverage for this new behavior.

Evidence

• grep across tests/ finds zero matches for control_flow, register_control_flow_exception, or should_be_treated_as_error.
• tests/integrations/aiohttp/test_aiohttp.py contains no references to HTTPException span-status behaviour.
• should_be_treated_as_error is called in both sentry_sdk/traces.py:335 and sentry_sdk/tracing.py:398 to set span status, making the untested path critical.

_{Identified by Warden code-review}

[linear-code]

PY-2492

[alexander-alderman-webb]

Nice not increasing API surface!

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit b81e07a. Configure here.}