Skip to content

feat!: default identify-style events to person processing on - #1247

Merged
eli-r-ph merged 39 commits into
v1from
eli/v1-identify-style-person-default
Nov 16, 2026
Merged

eli-r-ph merged 39 commits into
v1from
eli/v1-identify-style-person-default

Conversation

@eli-r-ph

@eli-r-ph eli-r-ph commented Nov 12, 2026 •

Copy link
Copy Markdown
Contributor

💡 Motivation and Context

In posthog-python 8.0, a process_person_profile: False set in super_options, super_properties, a context option or a context tag reaches alias, group_identify, set and set_once. PostHog then drops those events or ignores their person update, so an app that turns person processing off globally silently stops identifying users.

  • Identify-style events ($identify, $create_alias, $merge_dangerously, $groupidentify, $set, $set_once) now default to process_person_profile: True, from any method, unless the call sets it.
  • The call's own value still wins:
    • a call option is kept;
    • a call's $process_person_profile property becomes the option and is removed from the properties;
    • None counts as unset.
  • An event whose distinct ID the SDK generated keeps the personless False.
  • before_send sees the value and can change it. The default is decided from the event name the call used, so a hook that renames an event or builds an identify-style event sets the option itself.
  • One helper, _default_identify_style_person_processing in capture_event.py, runs at the top of _fill_event_defaults, before any layer, in both the sync and async clients.
  • A single personless flag replaces the old derived personless options, and drives both the personless layer and the generated-ID check.
  • At the end of _fill_event_defaults, a $process_person_profile property left by super_properties or a context tag is removed from these events once the option is set. before_send sees one value, and a hook that drops options can't bring back a layered False. The wire output is unchanged.
  • An explicit True reaches ingestion the same way as no value, except that it replaces a layered False. Server-side opt-outs still win.
  • The 8.0 guide replaces the per-call opt-in with the new rules. The 8.x and migration references and the docstrings are updated (--major 8). The existing identity-and-context-rules changeset gains the exception, with no new changeset, because this lands in 8.0.

💚 How did you test it?

  • New test_event_options.py cases, through the public API to the v1 wire payload, sync and async:
    • every emitter against each layer kind;
    • call option, call legacy property, None;
    • a generated ID, and the $<type>_<key> group fallback;
    • before_send seeing and changing the value;
    • a before_send rename;
    • non-identify events, which keep layered False;
    • caller dicts left unmutated.
  • Mutating the helper fails the new tests. The mutations included ignoring the generated-ID check, running after layers, dropping a name, prefix matching, and not passing the ID flag.
  • Existing tests that asserted the old options, and the event_family.json snapshot, are updated to the new behavior.
  • Local runs:
    • full pytest: 7,673 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 Opus 5.5) at Eli's direction, as part of the capture v1 release. The rule, the event list and the generated-ID exception were decided by Eli. The SDK-side check runs before any layer so only the call's own value counts. Always sending True was chosen over sending it only when a layer would set another value, because the backend treats an explicit True like an unset value for these events.

🤖 Generated with Claude Code

eli-r-ph and others added 16 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>
$identify, $create_alias, $merge_dangerously, $groupidentify, $set and
$set_once now resolve process_person_profile from the call alone before any
layer fills: a non-null call option wins, else a non-null call
$process_person_profile property moves into the option, else the option is
true unless the SDK generated the distinct ID. Context options and tags,
super_options and super_properties can no longer turn person processing off
for these events. before_send still sees the value and has the final say.

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

Replaces the guidance that layered process_person_profile false reaches
alias, group_identify, set and set_once and needs a per-call true, and
regenerates the 8.x and migration references.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@eli-r-ph eli-r-ph self-assigned this Nov 12, 2026
@github-actions

github-actions Bot commented Nov 12, 2026 •

Copy link
Copy Markdown
Contributor

SDK performance: posthog-python

1 change worth reviewing: 1 observed regression.

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.

Test Measurement Before PR With PR Change
Capture and deliver events (4,096-byte payload, steady) Process CPU time per operation 99.62 µs/op 105.06 µs/op 5.5% more time
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.2 KiB/op 133.68 KiB/op 0.4% more memory Not flagged
Capture and deliver events (32-byte payload, burst)
Shard: capture
Allocations per operation 1,337.51 count/op 1,345.51 count/op 0.6% more Not flagged
Capture and deliver events (32-byte payload, burst)
Shard: capture
Time per operation 76.42 µs/op 77.24 µs/op 1.1% more time Not flagged
Capture and deliver events (32-byte payload, burst)
Shard: capture
Idle process memory (RSS) 37.51 MiB 37.47 MiB 0.1% less memory Not flagged
Capture and deliver events (32-byte payload, burst)
Shard: capture
Observed peak process memory (RSS) 39.94 MiB 39.9 MiB 0.1% less memory Not flagged
Capture and deliver events (32-byte payload, burst)
Shard: capture
Process memory after settling (RSS) 39.94 MiB 39.9 MiB 0.1% less memory Not flagged
Capture and deliver events (32-byte payload, burst)
Shard: capture
Process CPU time per operation 80.28 µs/op 79.41 µs/op 1.1% less time Not flagged
Capture and deliver events (32-byte payload, burst)
Shard: capture
Lifetime peak process memory (RSS) 40.15 MiB 40.15 MiB No observed change Not flagged
Capture and deliver events (4,096-byte payload, burst)
Shard: capture
Allocated memory per operation 185.28 KiB/op 185.76 KiB/op 0.3% more memory Not flagged
Capture and deliver events (4,096-byte payload, burst)
Shard: capture
Allocations per operation 1,329.51 count/op 1,337.51 count/op 0.6% more Not flagged
Capture and deliver events (4,096-byte payload, burst)
Shard: capture
Time per operation 100.77 µs/op 101.61 µs/op 0.8% more time Not flagged
Capture and deliver events (4,096-byte payload, burst)
Shard: capture
Idle process memory (RSS) 41.13 MiB 41.15 MiB <0.1% more memory Not flagged
Capture and deliver events (4,096-byte payload, burst)
Shard: capture
Observed peak process memory (RSS) 46.88 MiB 46.9 MiB <0.1% more memory Not flagged
Capture and deliver events (4,096-byte payload, burst)
Shard: capture
Process memory after settling (RSS) 46.88 MiB 46.9 MiB <0.1% more memory Not flagged
Capture and deliver events (4,096-byte payload, burst)
Shard: capture
Process CPU time per operation 96.74 µs/op 98.71 µs/op 2% more time Not flagged
Capture and deliver events (4,096-byte payload, burst)
Shard: capture
Lifetime peak process memory (RSS) 51.27 MiB 51.33 MiB 0.1% more memory Not flagged
Capture and deliver events (32-byte payload, steady)
Shard: capture
Allocated memory per operation 138.25 KiB/op 138.74 KiB/op 0.4% more memory Not flagged
Capture and deliver events (32-byte payload, steady)
Shard: capture
Allocations per operation 1,382.28 count/op 1,390.3 count/op 0.6% more Not flagged
Capture and deliver events (32-byte payload, steady)
Shard: capture
Time per operation 88.79 µs/op 89.17 µs/op 0.4% more time Not flagged
Capture and deliver events (32-byte payload, steady)
Shard: capture
Idle process memory (RSS) 37.41 MiB 37.48 MiB 0.2% more memory Not flagged
Capture and deliver events (32-byte payload, steady)
Shard: capture
Observed peak process memory (RSS) 37.57 MiB 37.65 MiB 0.2% more memory Not flagged
Capture and deliver events (32-byte payload, steady)
Shard: capture
Process memory after settling (RSS) 37.57 MiB 37.65 MiB 0.2% more memory Not flagged
Capture and deliver events (32-byte payload, steady)
Shard: capture
Process CPU time per operation 90.43 µs/op 91.17 µs/op 0.8% more time Not flagged
Capture and deliver events (32-byte payload, steady)
Shard: capture
Lifetime peak process memory (RSS) 40.15 MiB 40.15 MiB No observed change Not flagged
Capture and deliver events (4,096-byte payload, steady)
Shard: capture
Allocated memory per operation 190.43 KiB/op 190.92 KiB/op 0.3% more memory Not flagged
Capture and deliver events (4,096-byte payload, steady)
Shard: capture
Allocations per operation 1,374.19 count/op 1,382.2 count/op 0.6% more Not flagged
Capture and deliver events (4,096-byte payload, steady)
Shard: capture
Time per operation 105.36 µs/op 106.86 µs/op 1.4% more time Not flagged
Capture and deliver events (4,096-byte payload, steady)
Shard: capture
Idle process memory (RSS) 40.86 MiB 40.95 MiB 0.2% more memory Not flagged
Capture and deliver events (4,096-byte payload, steady)
Shard: capture
Observed peak process memory (RSS) 41.32 MiB 41.42 MiB 0.2% more memory Not flagged
Capture and deliver events (4,096-byte payload, steady)
Shard: capture
Process memory after settling (RSS) 40.9 MiB 41 MiB 0.2% more memory Not flagged
Capture and deliver events (4,096-byte payload, steady)
Shard: capture
Process CPU time per operation 99.62 µs/op 105.06 µs/op 5.5% more time Worth reviewing: observed regression
Capture and deliver events (4,096-byte payload, steady)
Shard: capture
Lifetime peak process memory (RSS) 41.24 MiB 41.29 MiB 0.1% more memory Not flagged
Queue an event (32-byte payload)
Shard: capture
Caller-thread CPU time per operation 57.1 µs/op 57.62 µs/op 0.9% more time Not flagged
Queue an event (32-byte payload)
Shard: capture
Time per operation 57.1 µs/op 57.62 µs/op 0.9% more time Not flagged
Queue an event (4,096-byte payload)
Shard: capture
Caller-thread CPU time per operation 57.45 µs/op 58.03 µs/op 1% more time Not flagged
Queue an event (4,096-byte payload)
Shard: capture
Time per operation 57.44 µs/op 58.02 µs/op 1% more 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 76.98 µs/op 76.66 µs/op 0.4% less time Not flagged
Evaluate all 10 flags
Shard: flags-scaling
Process CPU time per operation 76.99 µs/op 76.67 µs/op 0.4% less 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 724.92 µs/op 726.37 µs/op 0.2% more time Not flagged
Evaluate all 100 flags
Shard: flags-scaling
Process CPU time per operation 724.97 µs/op 726.43 µs/op 0.2% 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 7.21 ms/op 7.18 ms/op 0.4% less time Not flagged
Evaluate all 1,000 flags
Shard: flags-scaling
Process CPU time per operation 7.2 ms/op 7.18 ms/op 0.4% less time Not flagged
Evaluate 1,000 flags under concurrent load
Shard: flags-memory
Idle process memory (RSS) 42.89 MiB 42.92 MiB <0.1% more memory Not flagged
Evaluate 1,000 flags under concurrent load
Shard: flags-memory
Observed peak process memory (RSS) 43.22 MiB 43.25 MiB <0.1% more memory Not flagged
Evaluate 1,000 flags under concurrent load
Shard: flags-memory
Process memory after settling (RSS) 43.22 MiB 43.25 MiB <0.1% more memory Not flagged
Evaluate 1,000 flags under concurrent load
Shard: flags-memory
Lifetime peak process memory (RSS) 43.61 MiB 43.71 MiB 0.2% more memory Not flagged
Refresh 1,000 flag definitions
Shard: flags-memory
Idle process memory (RSS) 43.01 MiB 43.02 MiB <0.1% more memory Not flagged
Refresh 1,000 flag definitions
Shard: flags-memory
Observed peak process memory (RSS) 43.02 MiB 43.03 MiB <0.1% more memory Not flagged
Refresh 1,000 flag definitions
Shard: flags-memory
Process memory after settling (RSS) 42.98 MiB 43.03 MiB 0.1% more memory Not flagged
Refresh 1,000 flag definitions
Shard: flags-memory
Lifetime peak process memory (RSS) 43.32 MiB 43.33 MiB <0.1% 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 7.99 µs/op 7.91 µs/op 1% less time Not flagged
Evaluate one boolean flag
Shard: flags-single
Process CPU time per operation 7.99 µs/op 7.91 µs/op 1% less 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 11.06 µs/op 11.08 µs/op 0.2% more time Not flagged
Evaluate a cohort-filtered flag
Shard: flags-single
Process CPU time per operation 11.06 µs/op 11.08 µs/op 0.2% more 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 15.77 µs/op 15.81 µs/op 0.3% more time Not flagged
Evaluate a flag (early match)
Shard: flags-single
Process CPU time per operation 15.77 µs/op 15.81 µs/op 0.3% 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 22.33 µs/op 22.46 µs/op 0.6% more time Not flagged
Evaluate a flag (late match)
Shard: flags-single
Process CPU time per operation 22.33 µs/op 22.46 µs/op 0.6% more 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 21.08 µs/op 21.11 µs/op 0.1% more time Not flagged
Evaluate a flag (no match)
Shard: flags-single
Process CPU time per operation 21.08 µs/op 21.11 µ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 9.09 µs/op 9.08 µs/op <0.1% less time Not flagged
Evaluate a property-filtered flag
Shard: flags-single
Process CPU time per operation 9.09 µs/op 9.08 µs/op <0.1% 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 9.59 µs/op 9.44 µs/op 1.6% less time Not flagged
Evaluate a regex-filtered flag
Shard: flags-single
Process CPU time per operation 9.59 µs/op 9.44 µs/op 1.6% less 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 7.5 µs/op 7.49 µs/op 0.2% less time Not flagged
Evaluate a rollout flag
Shard: flags-single
Process CPU time per operation 7.5 µs/op 7.49 µs/op 0.2% less 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 8.34 µs/op 8.29 µs/op 0.6% less time Not flagged
Evaluate a multivariate flag
Shard: flags-single
Process CPU time per operation 8.34 µs/op 8.29 µs/op 0.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 0ded23d0a96ef2f90e615e61fad7a88c8b69ddd1 → 5b249fb75375888ad74c5a15f1829d7523f2b8f1.

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 13:53
…vents

After the layers fill, an identify-style event whose process_person_profile
option is set loses its $process_person_profile property, so before_send
sees one value and a hook that drops options cannot send a layered legacy
false. Event defaults now take one personless flag, which sets both the
personless option layer and the generated-id check. Option layer
docstrings say they never set process_person_profile on these events.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Moves the release note into identity-and-context-rules, notes that before_send
sees only the option, and regenerates the 8.x and migration references.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Context options and super_options still fill process_person_profile on an
identify-style event whose distinct ID the SDK generated, so the release
note, guide, AGENTS.md and option docstrings now say so, and a test pins it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@eli-r-ph
eli-r-ph marked this pull request as ready for review November 12, 2026 22:26
@eli-r-ph
eli-r-ph requested a review from a team as a code owner November 12, 2026 22:26
@veria-ai

veria-ai Bot commented Nov 12, 2026 •

Copy link
Copy Markdown

PR overview

No security issues were found in this pull request.

Reviews

eli-r-ph and others added 6 commits November 12, 2026 14:54
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>
eli-r-ph and others added 6 commits November 12, 2026 15:01
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>
…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>
…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 and others added 8 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>
…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 3e804b9 into v1 Nov 16, 2026
129 checks passed
@eli-r-ph
eli-r-ph deleted the eli/v1-identify-style-person-default branch November 16, 2026 16:08
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