feat(pyreqwest): Support span streaming

[alexander-alderman-webb]

Description

In the streaming path, use

• code.filepath instead of code.file.path
• code.line.number instead of code.lineno
• url.full instead of url
• url.query instead of http.query
• url.fragment instead of http.fragment
• http.request.method instead of http.method

Adapting Tests

sed commands used for converting transaction context managers:

• sed -i '' 's/with start_transaction(name="test_transaction"):/with sentry_sdk.traces.start_span(name="custom parent"):/g'

sed commands used for converting specific attributes:

• sed -i '' 's/CODE_LINENO/CODE_LINE_NUMBER/g'
• sed -i '' 's/CODE_FILEPATH/CODE_FILE_PATH/g'
• sed -i '' 's/["url"]/["url.full"]/g'
• sed -i '' 's/HTTP_QUERY/URL_QUERY/g
• sed -i '' 's/HTTP_FRAGMENT/URL_FRAGMENT/g'

sed commands used for converting event capture:

• sed -i '' 's/event["spans"]/spans/g'
• sed -i '' 's/(event,) = events/spans = [item.payload for item in items if item.type == "span"]/g'
• sed -i '' 's/events = capture_events()/items = capture_items("event", "transaction", "span")/g'
• sed -i '' 's/capture_events,/capture_items,/g'

sed commands used for converting op:

• sed -i '' 's/["op"]/["attributes"]["sentry.op"]/g'

sed commands used for converting origin:

• sed -i '' 's/["origin"]/["attributes"]["sentry.origin"]/g'

sed commands used for converting description:

• sed -i '' 's/["description"]/["name"]/g'

sed commands used for converting data to attributes:

• sed -i '' 's/["data"]/["attributes"]/g'

other test changes:

• sed -i '' 's/assert len(spans) == 1/assert len(spans) == 2/g'

Issues

Reminders

• Please add tests to validate your changes, and lint your code using uv run ruff.
• 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 📊

✅ 88173 passed | ⏭️ 6009 skipped | Total: 94182 | Pass Rate: 93.62% | Execution Time: 298m 8s

📊 Comparison with Base Branch

Metric	Change
Total Tests	📈 +120
Passed Tests	📈 +120
Failed Tests	—
Skipped Tests	—

All tests are passing successfully.

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

Coverage diff

@@            Coverage Diff             @@
##          main       #PR       +/-##
==========================================
+ Coverage    89.96%    89.97%    +0.01%
==========================================
  Files          191       191         —
  Lines        23031     23055       +24
  Branches      7906      7920       +14
==========================================
+ Hits         20719     20742       +23
- Misses        2312      2313        +1
- Partials      1306      1307        +1

---

Generated by Codecov Action

[sentry-warden]

test_no_request_source_if_duration_too_short (streaming) checks the wrong span field, making assertions vacuously true

In the streaming branch of test_no_request_source_if_duration_too_short (test file line ~814), data = span.get("data", {}) should be span.get("attributes", {}). Streaming spans expose source code fields under "attributes" (as every other streaming test does), so "data" always returns {} and the not in assertions trivially pass — the test never validates that request-source data is actually absent. Additionally, the mocked _end_timestamp is set to microsecond=100001 (100.001 ms), which exceeds the 100 ms threshold, so if the key were corrected the test would fail because source data would be added; the timestamp should be set to something below the threshold (e.g. microsecond=99999) to match the intent of the non-streaming branch.

Evidence

• test_request_source_if_duration_over_threshold (streaming) uses span.get("attributes", {}) and asserts the keys are present — consistent with streaming spans storing data in "attributes".
• test_no_request_source_if_duration_too_short (streaming, line ~814) uses span.get("data", {}), which returns {} for streaming spans; not in {} is always True.
• Both tests mock _end_timestamp = datetime(2024, 1, 1, microsecond=100001) (100.001 ms). With http_request_source_threshold_ms=100, add_http_request_source evaluates 100.001 > 100 → True and adds source; the "too short" test's end timestamp should be microsecond=99999 (< 100 ms) to mirror the non-streaming branch's microsecond=99999.
• add_http_request_source is called inside the with sentry_sdk.traces.start_span() block after yield span, so _end_timestamp is still the mocked value (not yet reset to None) when the duration check runs.

_{Identified by Warden code-review}

[sentrivana]

LGTM! Would just remove the extra filtering by item.type == "span" in the tests where not necessary

[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 76b9dd6. Configure here.}