Releases: statsig-io/python-sdk
v0.12.2 - cleanup: patches caught exception in shutdown
shutdown tried to join on a phantom thread. The exception was caught and logged, but this cleans it up
v0.12.1 - Fixes event timestamp
Event timestamp was incorrectly statically set. So every event from the python SDK had the same timestamp. This fixes that bug
v0.12.0 - Adds clientInitializeResponse
Adds get_client_initialize_response(StatsigUser)
. This can be used to generate the initialize response for a given user to be used in a client SDK. If you compute this using the python server SDK, you can bootstrap a statsig client SDK with the result and remove a network round trip to statsig
Also ID list updates to improve reliability and monitoring
v0.11.0 - Adds event_queue_size to statsigoptions and wraps exceptions
Adds event_queue_size parameter to StatsigOptions to make the number of events to batch before flushing to Statsig configurable. Defaults to 500 as before.
Also, internally, wraps, catches, and logs exceptions to statsig via ErrorBoundary so we can debug errors
v0.10.3 - [internal] lower log level to warn
Rather than logging as exception, log internal SDK messages as warn
v0.10.2 - Fix Layer secondary exposure logging
We were logging the wrong secondary_exposure array on statsig::layer_exposure
v0.10.1 - typing updates continued
Type the singleton statsig methods
v0.10.0 - Updated SDK typing
Typing input as StatsigUser instead of object, typing log events, the value of log events as number or string, and optional types for nullable fields across StatsigOptions, StatsigUser, and StatsigEvent
v0.9.3 - fix time based operator
fixed "before" and "after" operator for Time based conditions
v0.9.2- remove userID requirement if customID is present
Now the SDK only requires either a userID or any customID