feat: add setup method #245
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
PR Summary
Added a new setup() function to explicitly initialize the PostHog client, improving reliability in environments like Celery where exception handling needs to be available before event tracking occurs.
- Extracted client initialization logic from
_proxy()into dedicatedsetup()function inposthog/__init__.py - Version bump to 4.3.3 in
posthog/version.pyto reflect this enhancement - Added safety measure for exception handlers to ensure they're initialized even without event capture
3 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings | Greptile
Contributor
Author
|
Kept hitting rebase issues with the changelog so folded this into #252 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We cannot guarantee that the default PostHog client is always created. This means things like exception autocapture handlers will not get set until some other function creates the client e.g. capture. Let's expose a function to setup the client for use in environments like Celery where we could potentially need to capture an exception event if no events are being captured