[7.2.0] - 2021-06-17
- The SDK now supports the ability to control the proportion of traffic allocation to an experiment. This works in conjunction with a new platform feature now available to early access customers.
[7.0.1] - 2020-11-25
- The logic for detecting uWSGI did not account for undocumented behavior in some environments where the
uwsgimodule is present in an incomplete state; this could cause an error on startup in such environments. Also, the log message about threading options related to uWSGI contained a broken link. (Thanks, andrefreitas!)
[7.0.0] - 2020-10-28
This major release is for Python compatibility updates and removal of deprecated APIs. It introduces no new functionality except type hints.
- Added type hints to all SDK methods. Python by itself does not enforce these, but commonly used development tools can provide static checking to trigger warnings or errors if the wrong type is used.
- Python 2.7, 3.3, and 3.4 are no longer supported. The minimum Python version is now 3.5.
- The first parameter to the
sdk_key, is now required. Previously it was possible to omit the
Configand specify it separately when initializing the SDK. Now, it is always in the
ldclient.set_sdk_key(). The correct way to do this now, if you are using the singleton client method
ldclient.get(), is to call
Configobject that contains the SDK key.
- Removed the optional SDK key parameter from the
LDClientconstructor. You must now provide a configuration parameter of type
Config, and set the SDK key within the
LDClient(Config(sdk_key = "my-sdk-key", [any other config options])). Previously, it was possible to specify the SDK key as a single string parameter and omit the
LDClient("my-sdk-key")—although this would cause a deprecation warning to be logged; specifying both a key and a
Configwas always an error.
- Removed the individual HTTP-related parameters such as
Configtype. The correct way to set these now is with the
Config(sdk_key = "my-sdk-key", http = HTTPConfig(connect_timeout = 10)).
- Removed all other types, parameters, and methods that were deprecated as of the last 6.x release.
[6.13.2] - 2020-09-21
- The SDK was not recognizing proxy authorization parameters included in a proxy URL (example:
http://username:password@proxyhost:port). It will now use these parameters if present, regardless of whether you set the proxy URL programmatically or in an environment variable. (Thanks, gangeli!)
[6.13.0] - 2020-03-30
- The new
initial_reconnect_delayallows customizing of the base retry delay for stream connections (that is, the delay for the first reconnection after a failure; subsequent retries use an exponential backoff).
- The new
HTTPConfigclass allow advanced configuration of the SDK's network behavior, such as specifying a custom certificate authority for connecting to a proxy/gateway that uses a self-signed certificate.
- The retry delay for stream connections has been changed as follows: it uses an exponential backoff no matter what type of error occurred (previously, some kinds of errors had a hard-coded 1-second delay), and each delay is reduced by a random jitter of 0-50% rather than 0-100%. Also, if a connection remains active for at least 60 seconds, the backoff is reset to the initial value. This makes the Python SDK's behavior consistent with other LaunchDarkly SDKs.
- The existing
verify_sslare now deprecated and superseded by the equivalent properties in
[6.12.2] - 2020-03-19
Falsein the client configuration did not have the expected effect of completely turning off SSL/TLS verification, because it still left certificate verification in effect, so it would allow a totally insecure connection but reject a secure connection whose certificate had an unknown CA. This has been changed so that it will turn off certificate verification as well. This is not a recommended practice and a future version of the SDK will add a way to specify a custom certificate authority instead (to support, for instance, using the Relay Proxy with a self-signed certificate).