gBddlZddlmZmZmZmZmZddlmZddl m Z ddl m Z e Z dZdZdZdZdZdZdZdZdZdZdZd ZdZdZgZdZdZda d d Z d!d Z! d!d Z" d!d Z# d!dZ$ d"dZ% d#dZ&iiidddfdZ'iiidddfdZ(iiiddfdZ)diiidddfdZ*iiiddfdZ+dZ,dZ-dZ.dZ/dZ0dZ1dZ2dZ3GddeZ4y)$N)CallableDictListOptionalTuple)Client) Integrations)VERSIONFTc ,td||||||||| S)a Capture allows you to capture anything a user does within your system, which you can later use in PostHog to find patterns in usage, work out which features to improve or where people are giving up. A `capture` call requires - `distinct id` which uniquely identifies your user - `event name` to specify the event - We recommend using [verb] [noun], like `movie played` or `movie updated` to easily identify what your events mean later on. Optionally you can submit - `properties`, which can be a dict with any information you'd like to add - `groups`, which is a dict of group type -> group key mappings For example: ```python posthog.capture('distinct id', 'opened app') posthog.capture('distinct id', 'movie played', {'movie_id': '123', 'category': 'romcom'}) posthog.capture('distinct id', 'purchase', groups={'company': 'id:5'}) ``` capture distinct_idevent propertiescontext timestampuuidgroupssend_feature_flags disable_geoip_proxyrs E/var/www/openai/venv/lib/python3.12/site-packages/posthog/__init__.pyrr#s0@  -#  c &td||||||S)a Identify lets you add metadata on your users so you can more easily identify who they are in PostHog, and even do things like segment users by these properties. An `identify` call requires - `distinct id` which uniquely identifies your user - `properties` with a dict with any key: value pairs For example: ```python posthog.identify('distinct id', { 'email': 'dwayne@gmail.com', 'name': 'Dwayne Johnson' }) ``` identifyrrrrrrrrs rrrQ&0  # rc &td||||||S)a Set properties on a user record. This will overwrite previous people property values, just like `identify`. A `set` call requires - `distinct id` which uniquely identifies your user - `properties` with a dict with any key: value pairs For example: ```python posthog.set('distinct id', { 'current_browser': 'Chrome', }) ``` setrrrs rr"r"ts&0   # rc &td||||||S)a Set properties on a user record, only if they do not yet exist. This will not overwrite previous people property values, unlike `identify`. A `set_once` call requires - `distinct id` which uniquely identifies your user - `properties` with a dict with any key: value pairs For example: ```python posthog.set_once('distinct id', { 'referred_by': 'friend', }) ``` set_oncerrrs rr$r$r rc (td|||||||S)aV Set properties on a group A `group_identify` call requires - `group_type` type of your group - `group_key` unique identifier of the group - `properties` with a dict with any key: value pairs For example: ```python posthog.group_identify('company', 5, { 'employees': 11, }) ``` group_identify group_type group_keyrrrrrrr's rr&r&s)2  #  rc &td||||||S)a- To marry up whatever a user does before they sign up or log in with what they do after you need to make an alias call. This will allow you to answer questions like "Which marketing channels leads to users churning after a month?" or "What do users do on our website before signing up?" In a purely back-end implementation, this means whenever an anonymous user does something, you'll want to send a session ID ([Django](https://stackoverflow.com/questions/526179/in-django-how-can-i-find-out-the-request-session-sessionid-and-use-it-as-a-vari), [Flask](https://stackoverflow.com/questions/15156132/flask-login-how-to-get-session-id)) with the capture call. Then, when that users signs up, you want to do an alias call with the session ID and the newly created user ID. The same concept applies for when a user logs in. An `alias` call requires - `previous distinct id` the unique ID of the user before - `distinct id` the current unique id For example: ```python posthog.alias('anonymous session id', 'distinct id') ``` alias previous_idrrrrrrr,s rr+r+s&2  # rc (td|||||||S)a capture_exception allows you to capture exceptions that happen in your code. This is useful for debugging and understanding what errors your users are encountering. This function never raises an exception, even if it fails to send the event. A `capture_exception` call does not require any fields, but we recommend sending: - `distinct id` which uniquely identifies your user for which this exception happens - `exception` to specify the exception to capture. If not provided, the current exception is captured via `sys.exc_info()` Optionally you can submit - `properties`, which can be a dict with any information you'd like to add - `groups`, which is a dict of group type -> group key mappings For example: ```python try: 1 / 0 except Exception as e: posthog.capture_exception(e, 'my specific distinct id') posthog.capture_exception(distinct_id='my specific distinct id') ``` capture_exception exceptionrrrrrrrr0s rr/r/s*@    rc *td|||||||| S)a Use feature flags to enable or disable features for users. For example: ```python if posthog.feature_enabled('beta feature', 'distinct id'): # do something if posthog.feature_enabled('groups feature', 'distinct id', groups={"organization": "5"}): # do something ``` You can call `posthog.load_feature_flags()` before to make sure you're not doing unexpected requests. feature_enabledkeyrrperson_propertiesgroup_propertiesonly_evaluate_locallysend_feature_flag_eventsrrr4s rr3r3/s,0  +)3!9#  rc *td|||||||| S)aJ Get feature flag variant for users. Used with experiments. Example: ```python if posthog.get_feature_flag('beta-feature', 'distinct_id') == 'test-variant': # do test variant code if posthog.get_feature_flag('beta-feature', 'distinct_id') == 'control': # do control code ``` `groups` are a mapping from group type to group key. So, if you have a group type of "organization" and a group key of "5", you would pass groups={"organization": "5"}. `group_properties` take the format: { group_type_name: { group_properties } } So, for example, if you have the group type "organization" and the group key "5", with the properties name, and employee count, you'll send these as: ```python group_properties={"organization": {"name": "PostHog", "employees": 11}} ``` get_feature_flagr4rr4s rr;r;Ts-@  +)3!9#  rc &td||||||S)z Get all flags for a given user. Example: ```python flags = posthog.get_all_flags('distinct_id') ``` flags are key-value pairs where the key is the flag key and the value is the flag variant, or True, or False. get_all_flagsrrr6r7r8rrr>s rr=r=s&" +)3# rc ,td||||||||| S)Nget_feature_flag_payload r5r match_valuerr6r7r8r9rrrAs rr@r@s/ " +)3!9#  rc &td||||||S)Nget_all_flags_and_payloadsr>rr>s rrDrDs& $+)3# rctdS)zbReturns loaded feature flags, if any. Helpful for debugging what flag information you have loaded.feature_flag_definitionsrrrrFrFs , --rctdS)z+Load feature flag definitions from PostHog.load_feature_flagsrrGrrrIrIs & ''rc"tdg|i|y)zSend a page call.pageNrargskwargss rrKrKs 6#D#F#rc"tdg|i|y)zSend a screen call.screenNrrLs rrPrPs 8%d%f%rctdy)zTell the client to flush.flushNrrGrrrRrRs  7Orctdy)z/Block program until the client clears the queuejoinNrrGrrrTrTs  6Nrc0tdtdy)z2Flush all messages and cleanly shutdown the clientrRrTNrrGrrshutdownrVs 7O 6Nrc&tsVttttt t tttttttttt att_ tt_t#t|}||i|S)z?Create an analytics client if one doesn't exist and send to it.)hostdebugon_errorsend sync_modepersonal_api_keyproject_api_key poll_intervaldisabledr%feature_flags_request_timeout_secondssuper_propertiesenable_exception_autocapture"exception_autocapture_integrations)default_clientrapi_keyrXrYrZr[r\r]r^r_r`rrarbrcrdgetattr)methodrMrNfns rrrso  -+''2W-*F/Q% ,'N N  (B t v rc eZdZy)PosthogN)__name__ __module__ __qualname__rGrrrkrksrrk)NNNNNFN)NNNNN)NNNN)NNNNNNN)5datetimetypingrrrrrposthog.clientrposthog.exception_capturer posthog.versionr __version__rfrXrZrYr[r\r`r]r^r_rrarbrcrd project_root privacy_modererrr"r$r&r+r/r3r;r=r@rDrFrIrKrPrRrTrVrrkrGrrrws88!2#          ()%$%'"     +`   J   J   L  "P   !J  )^ !"P !*^  > !6  &. ( $ &    B f r