6.12.0

[6.12.0] - 2020-02-11

Note: if you are using the LaunchDarkly Relay Proxy to forward events, update the Relay to version 5.10.0 or later before updating to this Python SDK version.

Added:

• The SDK now periodically sends diagnostic data to LaunchDarkly, describing the version and configuration of the SDK, the architecture and version of the runtime platform, and performance statistics. No credentials, hostnames, or other identifiable values are included. This behavior can be disabled with the diagnostic_opt_out option or configured with diagnostic_recording_interval.

Fixed:

• The SDK now specifies a uniquely identifiable request header when sending events to LaunchDarkly to ensure that events are only processed once, even if the SDK sends them two times due to a failed initial attempt.

6.11.3

[6.11.3] - 2019-12-30

Fixed:

• In rare circumstances (depending on the exact data in the flag configuration, the flag's salt value, and the user properties), a percentage rollout could fail and return a default value, logging the error "variation/rollout object with no variation or rollout". This would happen if the user's hashed value fell exactly at the end of the last "bucket" (the last variation defined in the rollout). This has been fixed so that the user will get the last variation.

6.11.2

[6.11.2] - 2019-12-09

Fixed:

• Changed Files.new_data_source() to use yaml.safe_load() instead of yaml.load() for YAML/JSON test data parsing. This disables pyyaml extended syntax features that could allow arbitrary code execution. (#136)

6.11.1

[6.11.1] - 2019-11-21

Fixed:

• Fixed an incompatibility with Python 3.3 due to an unpinned dependency on expiringdict.
• Fixed usages that caused a SyntaxWarning in Python 3.8. (Thanks, bunchesofdonald!)
• Updated CI scripts so a SyntaxWarning will always cause a build failure, and added a 3.8 build.

6.11.0

[6.11.0] - 2019-10-31

Added:

• The new Config parameter http_proxy allows you to specify a proxy server programmatically rather than by using environment variables. This may be helpful if you want the SDK to use a proxy, but do not want other Python code to use the proxy. (Thanks, gangeli!)

6.10.2

[6.10.2] - 2019-10-30

Fixed:

• Since version 6.1.0, the SDK was not respecting the standard https_proxy environment variable for specifying a proxy (because that variable is not used by urllib3). This has been fixed.
• In streaming mode, the SDK could fail to apply a feature flag update if it exceeded the LaunchDarkly service's maximum streaming message size; the service uses an alternate delivery mechanism in this case, which was broken in the SDK. This bug was also introduced in version 6.1.0.
• Fixed the generated documentation to exclude special members like __dict__.

6.10.1

[6.10.1] - 2019-08-20

Fixed:

• Fixed a bug in 6.10.0 that prevented analytics events from being generated for missing flags.

6.10.0

[6.10.0] - 2019-08-20

Added:

• Added support for upcoming LaunchDarkly experimentation features. See LDClient.track().

6.9.4

[6.9.4] - 2019-08-19

Fixed:

• Under conditions where analytics events are being generated at an extremely high rate (for instance, if an application is evaluating a flag repeatedly in a tight loop on many threads), a thread could be blocked indefinitely within variation while waiting for the internal event processing logic to catch up with the backlog. The logic has been changed to drop events if necessary so threads will not be blocked (similar to how the SDK already drops events if the size of the event buffer is exceeded). If that happens, this warning message will be logged once: "Events are being produced faster than they can be processed; some events will be dropped". Under normal conditions this should never happen; this change is meant to avoid a concurrency bottleneck in applications that are already so busy that thread starvation is likely.

6.9.3

[6.9.3] - 2019-06-11

Fixed:

• Usages of Logger.warn() were causing deprecation warnings in some versions of Python. Changed these to Logger.warning(). (#125)