Repository navigation
docs: point the new_context contexts link at the SDK reference - #1272
Conversation
The hand-written /docs/libraries/python page is retired, so its #contexts anchor no longer exists. Link to the posthog.new_context reference entry, which the Flask and Django docs already use. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
SDK performance: posthog-pythonBenchmarks 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
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 102 metric rows; 102 rows shown in all results. Omitted or shortened data remain in |
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The
Client.new_contextdocstring links/docs/libraries/python#contexts. posthog.com retired the hand-written Python page in PostHog/posthog.com#22061, so that anchor no longer exists. 8.0.x ships the broken link in its SDK reference.This PR points the link at
/docs/libraries/python#posthognew_context. That path redirects to the reference page, and the browser keeps the anchor.It changes the docstring and the same line in the three generated reference files (
7,8, andreference). The older versioned JSON files stay as they are.Replaces #1263, which was cut from the old
v1branch.🤖 Generated with Claude Code