Skip to content

feat: give CaptureError.drops entries named fields - #1248

Merged
eli-r-ph merged 31 commits into
eli/v1-identify-style-person-defaultfrom
eli/v1-capture-dropped-event
Nov 16, 2026
Merged

eli-r-ph merged 31 commits into
eli/v1-identify-style-person-defaultfrom
eli/v1-capture-dropped-event

Conversation

@eli-r-ph

Copy link
Copy Markdown
Contributor

💡 Motivation and Context

CaptureError.drops is a list of bare (uuid, details) tuples, so an on_error handler has to index them by position. 8.0 renames the error type, which makes this the right release to name the fields. Stacked on #1247.

  • Each entry of CaptureError.drops is now a CaptureDroppedEvent named tuple with uuid and details, exported from posthog.capture_send next to CaptureEventResult.
  • It is still a tuple, so code that unpacks, compares or sorts (uuid, details) pairs is unaffected.
  • CaptureError(drops=...) still accepts plain tuples and converts them.
  • The existing duplicate-event-uuid changeset gains one sentence, with no new changeset, because this lands in 8.0.

💚 How did you test it?

  • test_capture_send.py: the send path and a hand-built CaptureError both expose uuid and details. Removing the conversion fails both new assertions.
  • The existing assertions that compare drops to plain tuples pass unchanged.
  • Local runs:
    • full pytest: 7,750 passed; 3 failed, the macOS-only fork tests in test_metrics_autocapture.py, which fail identically on v1;
    • ruff check, ruff format --check, mypy, make public_api_check: all pass.

📝 Checklist

  • All commits are signed (see Commit signing)
  • I reviewed the submitted code.
  • I added tests to verify the changes.
  • I updated the docs if needed.
  • No breaking change or entry added to the changelog.

If releasing new changes

  • Ran sampo add to generate a changeset file (not needed: an existing 8.0 changeset is updated)

🤖 Agent context

Autonomy: Human-driven (agent-assisted)

Written with Claude Code (Claude Fable 5.2) at Eli's direction, from a public API review of the 8.0 branch. A named tuple was chosen over a dataclass so existing tuple handling, including the compliance adapter, keeps working.

🤖 Generated with Claude Code

eli-r-ph and others added 23 commits November 11, 2026 08:59
The migration guide is also published on posthog.com, where the relative
link resolves to a missing page.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit f143283)
The posthog.com Python SDK pages redirect to this reference once 8.0.0
ships, so their setup, how-to, and configuration sections now live in
docs/getting-started.md.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 9db7014)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 0e9f755)
…other page has

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The reference renders each docstring under its entry, per major, so the
tracing, ASGI, keepalive, and AsyncPosthog facts now live there.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Keeps both new generator functions (migration_page, getting_started) and
their tests. The guide keeps this branch's text; its Celery eager line
already carries #1232's wording.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…rted guide

The sorted 8.0.0 guide dropped facts the v1 guide states: the self-hosted
capture v1 route check, the 404 hint, the 400 duplicate_event_uuid on older
PostHog, the legacy path removal, and NaN as null since 7.75.0.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…rted guide

Identify-style events now default process_person_profile to true unless
the call sets it or the SDK generated the distinct ID, so layered false no
longer reaches them. Replaces the old reach rules and opt-in sample, and
updates the checklist row, precedence step 1 and the before_send section.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
start_span evicts spans older than max_span_age first and returns an
unrecorded span only if still at max_live_spans. A full span keeps the
exception message in its status and loses only the type and stack trace.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Generated with bin/docs_scripts/generate_markdown.py --major 8. The
migration page now carries the sorted guide, which it had not before.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…onless

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…he option

Only capture and capture_ai take event properties. The properties of set,
set_once and group_identify are person and group properties.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Each entry is now a CaptureDroppedEvent named tuple with uuid and details, so
code that unpacks or compares (uuid, details) tuples keeps working.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@eli-r-ph
eli-r-ph requested a review from a team as a code owner November 13, 2026 00:29
@eli-r-ph eli-r-ph self-assigned this Nov 13, 2026
@veria-ai

veria-ai Bot commented Nov 13, 2026 •

Copy link
Copy Markdown

PR overview

No security issues were found in this pull request.

Reviews

@github-actions

Copy link
Copy Markdown
Contributor

SDK performance: posthog-python

Benchmarks completed. No changes flagged for review.

Flags require at least a 5% change in the median and all six pairs agreeing on direction. This is a noise filter, not proof of a performance change or a CI gate.

View all results
Test Measurement Before PR With PR Change Assessment
Capture and deliver events (32-byte payload, burst)
Shard: capture
Managed heap after settling — — — unavailable; base:​ unsupported; head:​ unsupported; base:​ CPython has no uninstrumented total managed-heap byte counter; tracing would distort this RSS pass.​; head:​ CPython has no uninstrumented total managed-heap byte counter; tracing would distort this RSS pass.​
Capture and deliver events (4,096-byte payload, burst)
Shard: capture
Managed heap after settling — — — unavailable; base:​ unsupported; head:​ unsupported; base:​ CPython has no uninstrumented total managed-heap byte counter; tracing would distort this RSS pass.​; head:​ CPython has no uninstrumented total managed-heap byte counter; tracing would distort this RSS pass.​
Capture and deliver events (32-byte payload, steady)
Shard: capture
Managed heap after settling — — — unavailable; base:​ unsupported; head:​ unsupported; base:​ CPython has no uninstrumented total managed-heap byte counter; tracing would distort this RSS pass.​; head:​ CPython has no uninstrumented total managed-heap byte counter; tracing would distort this RSS pass.​
Capture and deliver events (4,096-byte payload, steady)
Shard: capture
Managed heap after settling — — — unavailable; base:​ unsupported; head:​ unsupported; base:​ CPython has no uninstrumented total managed-heap byte counter; tracing would distort this RSS pass.​; head:​ CPython has no uninstrumented total managed-heap byte counter; tracing would distort this RSS pass.​
Queue an event (32-byte payload)
Shard: capture
Allocated memory per operation — — — unavailable; base:​ unsupported; head:​ unsupported; base:​ Background preparation has no public completion boundary before flush; see capture.​drain for full-pipeline allocations.​; head:​ Background preparation has no public completion boundary before flush; see capture.​drain for full-pipeline allocations.​
Queue an event (32-byte payload)
Shard: capture
Allocations per operation — — — unavailable; base:​ unsupported; head:​ unsupported; base:​ Background preparation has no public completion boundary before flush; see capture.​drain for full-pipeline allocations.​; head:​ Background preparation has no public completion boundary before flush; see capture.​drain for full-pipeline allocations.​
Queue an event (4,096-byte payload)
Shard: capture
Allocated memory per operation — — — unavailable; base:​ unsupported; head:​ unsupported; base:​ Background preparation has no public completion boundary before flush; see capture.​drain for full-pipeline allocations.​; head:​ Background preparation has no public completion boundary before flush; see capture.​drain for full-pipeline allocations.​
Queue an event (4,096-byte payload)
Shard: capture
Allocations per operation — — — unavailable; base:​ unsupported; head:​ unsupported; base:​ Background preparation has no public completion boundary before flush; see capture.​drain for full-pipeline allocations.​; head:​ Background preparation has no public completion boundary before flush; see capture.​drain for full-pipeline allocations.​
Evaluate 1,000 flags under concurrent load
Shard: flags-memory
Managed heap after settling — — — unavailable; base:​ unsupported; head:​ unsupported; base:​ CPython has no uninstrumented total managed-heap byte counter; tracing would distort this RSS pass.​; head:​ CPython has no uninstrumented total managed-heap byte counter; tracing would distort this RSS pass.​
Refresh 1,000 flag definitions
Shard: flags-memory
Managed heap after settling — — — unavailable; base:​ unsupported; head:​ unsupported; base:​ CPython has no uninstrumented total managed-heap byte counter; tracing would distort this RSS pass.​; head:​ CPython has no uninstrumented total managed-heap byte counter; tracing would distort this RSS pass.​
Capture and deliver events (32-byte payload, burst)
Shard: capture
Allocated memory per operation 133.69 KiB/op 133.69 KiB/op <0.1% less memory Not flagged
Capture and deliver events (32-byte payload, burst)
Shard: capture
Allocations per operation 1,345.53 count/op 1,345.53 count/op <0.1% fewer Not flagged
Capture and deliver events (32-byte payload, burst)
Shard: capture
Time per operation 82.78 µs/op 82.79 µs/op <0.1% more time Not flagged
Capture and deliver events (32-byte payload, burst)
Shard: capture
Idle process memory (RSS) 37.58 MiB 37.56 MiB <0.1% less memory Not flagged
Capture and deliver events (32-byte payload, burst)
Shard: capture
Observed peak process memory (RSS) 40.01 MiB 39.99 MiB <0.1% less memory Not flagged
Capture and deliver events (32-byte payload, burst)
Shard: capture
Process memory after settling (RSS) 40.01 MiB 39.99 MiB <0.1% less memory Not flagged
Capture and deliver events (32-byte payload, burst)
Shard: capture
Process CPU time per operation 82.2 µs/op 82.2 µs/op <0.1% more time Not flagged
Capture and deliver events (32-byte payload, burst)
Shard: capture
Lifetime peak process memory (RSS) 40.26 MiB 40.29 MiB <0.1% more memory Not flagged
Capture and deliver events (4,096-byte payload, burst)
Shard: capture
Allocated memory per operation 185.76 KiB/op 185.76 KiB/op No observed change Not flagged
Capture and deliver events (4,096-byte payload, burst)
Shard: capture
Allocations per operation 1,337.52 count/op 1,337.52 count/op No observed change Not flagged
Capture and deliver events (4,096-byte payload, burst)
Shard: capture
Time per operation 103.17 µs/op 104.34 µs/op 1.1% more time Not flagged
Capture and deliver events (4,096-byte payload, burst)
Shard: capture
Idle process memory (RSS) 41.23 MiB 41.17 MiB 0.2% less memory Not flagged
Capture and deliver events (4,096-byte payload, burst)
Shard: capture
Observed peak process memory (RSS) 46.98 MiB 46.93 MiB 0.1% less memory Not flagged
Capture and deliver events (4,096-byte payload, burst)
Shard: capture
Process memory after settling (RSS) 46.98 MiB 46.93 MiB 0.1% less memory Not flagged
Capture and deliver events (4,096-byte payload, burst)
Shard: capture
Process CPU time per operation 97.46 µs/op 98.27 µs/op 0.8% more time Not flagged
Capture and deliver events (4,096-byte payload, burst)
Shard: capture
Lifetime peak process memory (RSS) 51.44 MiB 51.42 MiB <0.1% less memory Not flagged
Capture and deliver events (32-byte payload, steady)
Shard: capture
Allocated memory per operation 138.75 KiB/op 138.74 KiB/op <0.1% less memory Not flagged
Capture and deliver events (32-byte payload, steady)
Shard: capture
Allocations per operation 1,390.38 count/op 1,390.36 count/op <0.1% fewer Not flagged
Capture and deliver events (32-byte payload, steady)
Shard: capture
Time per operation 94.22 µs/op 93.48 µs/op 0.8% less time Not flagged
Capture and deliver events (32-byte payload, steady)
Shard: capture
Idle process memory (RSS) 37.54 MiB 37.54 MiB <0.1% less memory Not flagged
Capture and deliver events (32-byte payload, steady)
Shard: capture
Observed peak process memory (RSS) 37.7 MiB 37.7 MiB No observed change Not flagged
Capture and deliver events (32-byte payload, steady)
Shard: capture
Process memory after settling (RSS) 37.7 MiB 37.7 MiB No observed change Not flagged
Capture and deliver events (32-byte payload, steady)
Shard: capture
Process CPU time per operation 91.19 µs/op 90.46 µs/op 0.8% less time Not flagged
Capture and deliver events (32-byte payload, steady)
Shard: capture
Lifetime peak process memory (RSS) 40.12 MiB 40.12 MiB No observed change Not flagged
Capture and deliver events (4,096-byte payload, steady)
Shard: capture
Allocated memory per operation 190.92 KiB/op 190.92 KiB/op <0.1% less memory Not flagged
Capture and deliver events (4,096-byte payload, steady)
Shard: capture
Allocations per operation 1,382.28 count/op 1,382.27 count/op <0.1% fewer Not flagged
Capture and deliver events (4,096-byte payload, steady)
Shard: capture
Time per operation 109.42 µs/op 110.18 µs/op 0.7% more time Not flagged
Capture and deliver events (4,096-byte payload, steady)
Shard: capture
Idle process memory (RSS) 41.07 MiB 41 MiB 0.2% less memory Not flagged
Capture and deliver events (4,096-byte payload, steady)
Shard: capture
Observed peak process memory (RSS) 41.53 MiB 41.46 MiB 0.2% less memory Not flagged
Capture and deliver events (4,096-byte payload, steady)
Shard: capture
Process memory after settling (RSS) 41.11 MiB 41.05 MiB 0.2% less memory Not flagged
Capture and deliver events (4,096-byte payload, steady)
Shard: capture
Process CPU time per operation 103.51 µs/op 103.82 µs/op 0.3% more time Not flagged
Capture and deliver events (4,096-byte payload, steady)
Shard: capture
Lifetime peak process memory (RSS) 41.44 MiB 41.46 MiB <0.1% more memory Not flagged
Queue an event (32-byte payload)
Shard: capture
Caller-thread CPU time per operation 65.05 µs/op 63.55 µs/op 2.3% less time Not flagged
Queue an event (32-byte payload)
Shard: capture
Time per operation 65.05 µs/op 63.54 µs/op 2.3% less time Not flagged
Queue an event (4,096-byte payload)
Shard: capture
Caller-thread CPU time per operation 64.81 µs/op 63.64 µs/op 1.8% less time Not flagged
Queue an event (4,096-byte payload)
Shard: capture
Time per operation 65.1 µs/op 63.64 µs/op 2.2% less time Not flagged
Evaluate all 10 flags
Shard: flags-scaling
Allocated memory per operation 200.98 KiB/op 200.98 KiB/op No observed change Not flagged
Evaluate all 10 flags
Shard: flags-scaling
Allocations per operation 2,339.33 count/op 2,339.33 count/op No observed change Not flagged
Evaluate all 10 flags
Shard: flags-scaling
Time per operation 123.63 µs/op 123.73 µs/op <0.1% more time Not flagged
Evaluate all 10 flags
Shard: flags-scaling
Process CPU time per operation 123.63 µs/op 123.74 µs/op <0.1% more time Not flagged
Evaluate all 100 flags
Shard: flags-scaling
Allocated memory per operation 1.93 MiB/op 1.93 MiB/op No observed change Not flagged
Evaluate all 100 flags
Shard: flags-scaling
Allocations per operation 23,013.56 count/op 23,013.56 count/op No observed change Not flagged
Evaluate all 100 flags
Shard: flags-scaling
Time per operation 1.15 ms/op 1.16 ms/op 0.8% more time Not flagged
Evaluate all 100 flags
Shard: flags-scaling
Process CPU time per operation 1.15 ms/op 1.16 ms/op 0.8% more time Not flagged
Evaluate all 1,000 flags
Shard: flags-scaling
Allocated memory per operation 19.24 MiB/op 19.24 MiB/op No observed change Not flagged
Evaluate all 1,000 flags
Shard: flags-scaling
Allocations per operation 229,654.94 count/op 229,654.94 count/op No observed change Not flagged
Evaluate all 1,000 flags
Shard: flags-scaling
Time per operation 11.72 ms/op 11.75 ms/op 0.3% more time Not flagged
Evaluate all 1,000 flags
Shard: flags-scaling
Process CPU time per operation 11.72 ms/op 11.75 ms/op 0.3% more time Not flagged
Evaluate 1,000 flags under concurrent load
Shard: flags-memory
Idle process memory (RSS) 42.96 MiB 43.04 MiB 0.2% more memory Not flagged
Evaluate 1,000 flags under concurrent load
Shard: flags-memory
Observed peak process memory (RSS) 43.29 MiB 43.35 MiB 0.1% more memory Not flagged
Evaluate 1,000 flags under concurrent load
Shard: flags-memory
Process memory after settling (RSS) 43.29 MiB 43.35 MiB 0.1% more memory Not flagged
Evaluate 1,000 flags under concurrent load
Shard: flags-memory
Lifetime peak process memory (RSS) 43.72 MiB 43.77 MiB 0.1% more memory Not flagged
Refresh 1,000 flag definitions
Shard: flags-memory
Idle process memory (RSS) 43.07 MiB 43.07 MiB No observed change Not flagged
Refresh 1,000 flag definitions
Shard: flags-memory
Observed peak process memory (RSS) 43.08 MiB 43.08 MiB No observed change Not flagged
Refresh 1,000 flag definitions
Shard: flags-memory
Process memory after settling (RSS) 43.08 MiB 43.08 MiB No observed change Not flagged
Refresh 1,000 flag definitions
Shard: flags-memory
Lifetime peak process memory (RSS) 42.87 MiB 43.23 MiB 0.8% more memory Not flagged
Evaluate one boolean flag
Shard: flags-single
Allocated memory per operation 15.06 KiB/op 15.06 KiB/op No observed change Not flagged
Evaluate one boolean flag
Shard: flags-single
Allocations per operation 173.76 count/op 173.76 count/op No observed change Not flagged
Evaluate one boolean flag
Shard: flags-single
Time per operation 12.57 µs/op 12.64 µs/op 0.5% more time Not flagged
Evaluate one boolean flag
Shard: flags-single
Process CPU time per operation 12.57 µs/op 12.64 µs/op 0.5% more time Not flagged
Evaluate a cohort-filtered flag
Shard: flags-single
Allocated memory per operation 23.14 KiB/op 23.14 KiB/op No observed change Not flagged
Evaluate a cohort-filtered flag
Shard: flags-single
Allocations per operation 270.27 count/op 270.27 count/op No observed change Not flagged
Evaluate a cohort-filtered flag
Shard: flags-single
Time per operation 16.96 µs/op 16.76 µs/op 1.1% less time Not flagged
Evaluate a cohort-filtered flag
Shard: flags-single
Process CPU time per operation 16.96 µs/op 16.76 µs/op 1.1% less time Not flagged
Evaluate a flag (early match)
Shard: flags-single
Allocated memory per operation 35.73 KiB/op 35.73 KiB/op No observed change Not flagged
Evaluate a flag (early match)
Shard: flags-single
Allocations per operation 387.27 count/op 387.27 count/op No observed change Not flagged
Evaluate a flag (early match)
Shard: flags-single
Time per operation 24.07 µs/op 24.18 µs/op 0.5% more time Not flagged
Evaluate a flag (early match)
Shard: flags-single
Process CPU time per operation 24.07 µs/op 24.18 µs/op 0.5% more time Not flagged
Evaluate a flag (late match)
Shard: flags-single
Allocated memory per operation 53.61 KiB/op 53.61 KiB/op No observed change Not flagged
Evaluate a flag (late match)
Shard: flags-single
Allocations per operation 576.27 count/op 576.27 count/op No observed change Not flagged
Evaluate a flag (late match)
Shard: flags-single
Time per operation 34.23 µs/op 33.95 µs/op 0.8% less time Not flagged
Evaluate a flag (late match)
Shard: flags-single
Process CPU time per operation 34.23 µs/op 33.95 µs/op 0.8% less time Not flagged
Evaluate a flag (no match)
Shard: flags-single
Allocated memory per operation 52.16 KiB/op 52.16 KiB/op No observed change Not flagged
Evaluate a flag (no match)
Shard: flags-single
Allocations per operation 556.77 count/op 556.77 count/op No observed change Not flagged
Evaluate a flag (no match)
Shard: flags-single
Time per operation 32.34 µs/op 32.38 µs/op 0.1% more time Not flagged
Evaluate a flag (no match)
Shard: flags-single
Process CPU time per operation 32.34 µs/op 32.38 µs/op 0.1% more time Not flagged
Evaluate a property-filtered flag
Shard: flags-single
Allocated memory per operation 17.85 KiB/op 17.85 KiB/op No observed change Not flagged
Evaluate a property-filtered flag
Shard: flags-single
Allocations per operation 198.27 count/op 198.27 count/op No observed change Not flagged
Evaluate a property-filtered flag
Shard: flags-single
Time per operation 13.99 µs/op 13.94 µs/op 0.4% less time Not flagged
Evaluate a property-filtered flag
Shard: flags-single
Process CPU time per operation 13.99 µs/op 13.94 µs/op 0.4% less time Not flagged
Evaluate a regex-filtered flag
Shard: flags-single
Allocated memory per operation 19.24 KiB/op 19.24 KiB/op No observed change Not flagged
Evaluate a regex-filtered flag
Shard: flags-single
Allocations per operation 210.77 count/op 210.77 count/op No observed change Not flagged
Evaluate a regex-filtered flag
Shard: flags-single
Time per operation 14.87 µs/op 15.02 µs/op 1% more time Not flagged
Evaluate a regex-filtered flag
Shard: flags-single
Process CPU time per operation 14.87 µs/op 15.02 µs/op 1% more time Not flagged
Evaluate a rollout flag
Shard: flags-single
Allocated memory per operation 14.05 KiB/op 14.05 KiB/op No observed change Not flagged
Evaluate a rollout flag
Shard: flags-single
Allocations per operation 160.76 count/op 160.76 count/op No observed change Not flagged
Evaluate a rollout flag
Shard: flags-single
Time per operation 11.78 µs/op 11.81 µs/op 0.2% more time Not flagged
Evaluate a rollout flag
Shard: flags-single
Process CPU time per operation 11.78 µs/op 11.81 µs/op 0.2% more time Not flagged
Evaluate a multivariate flag
Shard: flags-single
Allocated memory per operation 15.22 KiB/op 15.22 KiB/op No observed change Not flagged
Evaluate a multivariate flag
Shard: flags-single
Allocations per operation 177.77 count/op 177.77 count/op No observed change Not flagged
Evaluate a multivariate flag
Shard: flags-single
Time per operation 13.2 µs/op 12.98 µs/op 1.6% less time Not flagged
Evaluate a multivariate flag
Shard: flags-single
Process CPU time per operation 13.2 µs/op 12.98 µs/op 1.6% less time Not flagged

Values are medians of paired measurements. Not flagged does not mean unchanged. Unavailable means a measurement could not be provided, not zero. Estimated allocation measurements retain their instrumentation uncertainty. RSS measures the whole process, not just SDK allocations; observed peaks are sampled checkpoints. Paired ranges in the diagnostics describe variability, not confidence intervals.

Each shard uses its own runner; compare Before PR against With PR within a row, not across shards.

Compared 93caef7637f497fc0ef6af561a9de03d44e71212 → ad010c5668d5cc62a81169d805d4d631249b2e84.

Full report and diagnostics

102 metric rows; 102 rows shown in all results. Omitted or shortened data remain in comparison.json, including per-runner environments, resource limits, measurement methods, samples and checkpoints.

eli-r-ph and others added 3 commits November 12, 2026 16:58
…-structure

Stacks the sorted guide on the identify-style person processing default and
the CaptureDroppedEvent change. The guide keeps the sorted text, which already
describes the default. References regenerated.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
…he guide

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Compression formats including zstd, the proxy pass-through rule, and that a
`$set` in a global or context layer reaches every event.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
gewenyu99 and others added 5 commits November 13, 2026 11:11
…es and semicolons

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The 8.x page is titled "PostHog Python SDK 8.x" before and after the release.
Regenerating also picks up the self-hosted paragraph the migration guide's source
already dropped.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…identify

"so set the option there" read as setting it in properties, where the SDK
treats it as a person property. set, set_once, and group_identify take
options, so the guide now names them.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Vincent ruled out self-hosted framing in the guides, and the endpoint and 404 sentences read as self-host framing. The retry tables and the proxy notes stay.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@eli-r-ph
eli-r-ph merged commit 5b249fb into eli/v1-identify-style-person-default Nov 16, 2026
47 checks passed
@eli-r-ph
eli-r-ph deleted the eli/v1-capture-dropped-event branch November 16, 2026 15:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants