fix: change scoped export, add capturing param

[oliverb123]

Figured while I was here we may as well let people use the tagging infrastructure without forcing them to use error tracking - it seems like a nice pattern for using posthog generally.

I do think we should default opt-in to error tracking tho - if we get complaints, we can expose a global config to disable it at the client level, but capturing exceptions in the most deeply nested context means getting the most tags on them, which is the ideal scenario.

[greptile-apps]

PR Summary

Updates scoping functionality in PostHog Python SDK to make error tracking optional while retaining tagging infrastructure.

• Added new capturing parameter to new_context and scoped functions, defaulting to True for backward compatibility
• Renamed exported decorator from tracked to scoped in posthog/__init__.py for better clarity
• Incremented version from 4.7.0 to 4.8.0 to reflect new functionality
• Maintained tag isolation and context inheritance behavior while making error tracking optional

_{4 files reviewed, no comments
Edit PR Review Bot Settings | Greptile}

[daibhin]

We could default to enable_exception_autocapture if this is not set

[oliverb123]

Huh, for some reason I thought that was client specific?

[daibhin]

It can be globally set using the proxy if the customer has configured their setup like

import posthog

posthog.enable_exception_autocapture = True

If that is None we should default (probably to True)

[oliverb123]

Defaults to False rather than None, sadly :/.

[oliverb123]

I think, given if we deferred to the global setting it'd always be off, it's good enough for now to default to on and let users disable. We can revisit it later, if we decide it's warranted

More broadly, I dislike complex behaviours and global configurations taking precedence over local ones - there may be good reasons a user wants to say "absolutely do not autocapture exceptions at this scope level", and we should respect it, imo.