Skip to content

@LaunchDarklyCI LaunchDarklyCI released this Jun 17, 2021

[7.2.0] - 2021-06-17

Added:

  • 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.
Assets 2

@LaunchDarklyCI LaunchDarklyCI released this Mar 12, 2021

[7.1.0] - 2021-03-11

Added:

  • Added the alias method to LDClient. This can be used to associate two user objects for analytics purposes with an alias event.
Assets 2

@LaunchDarklyCI LaunchDarklyCI released this Feb 23, 2021

[6.13.3] - 2021-02-23

Fixed:

  • The SDK could fail to send debug events when event debugging was enabled on the LaunchDarkly dashboard, if the application server's time zone was not GMT.
Assets 2

@LaunchDarklyCI LaunchDarklyCI released this Feb 19, 2021

[7.0.2] - 2021-02-18

Fixed:

  • The SDK could fail to send debug events when event debugging was enabled on the LaunchDarkly dashboard, if the application server's time zone was not GMT.
Assets 2

@LaunchDarklyCI LaunchDarklyCI released this Nov 26, 2020

[7.0.1] - 2020-11-25

Fixed:

  • The logic for detecting uWSGI did not account for undocumented behavior in some environments where the uwsgi module 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!)
Assets 2

@LaunchDarklyCI LaunchDarklyCI released this Oct 28, 2020

[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:

  • 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.

Changed:

  • 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 Config constructor, sdk_key, is now required. Previously it was possible to omit the sdk_key from the Config and specify it separately when initializing the SDK. Now, it is always in the Config.

Removed:

  • Removed ldclient.set_sdk_key(). The correct way to do this now, if you are using the singleton client method ldclient.get(), is to call ldclient.set_config() with a Config object that contains the SDK key.
  • Removed the optional SDK key parameter from the LDClient constructor. You must now provide a configuration parameter of type Config, and set the SDK key within the Config constructor: 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 Config object—LDClient("my-sdk-key")—although this would cause a deprecation warning to be logged; specifying both a key and a Config was always an error.
  • Removed the individual HTTP-related parameters such as connect_timeout from the Config type. The correct way to set these now is with the HTTPConfig sub-configuration object: 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.
Assets 2

@LaunchDarklyCI LaunchDarklyCI released this Sep 21, 2020

[6.13.2] - 2020-09-21

Fixed:

  • 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!)
Assets 2

@LaunchDarklyCI LaunchDarklyCI released this Jul 13, 2020

[6.13.1] - 2020-07-13

Fixed:

  • A problem with the SDK's use of urllib3.Retry could prevent analytics event delivery from being retried after a network error or server error. (#143)
Assets 2

@LaunchDarklyCI LaunchDarklyCI released this Mar 30, 2020

[6.13.0] - 2020-03-30

Added:

  • The new Config parameter initial_reconnect_delay allows 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 Config parameter http and the HTTPConfig class 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.

Changed:

  • 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.

Deprecated:

  • The existing Config properties connect_timeout, read_timeout, and verify_ssl are now deprecated and superseded by the equivalent properties in HTTPConfig.
Assets 2

@LaunchDarklyCI LaunchDarklyCI released this Mar 20, 2020

[6.12.2] - 2020-03-19

Fixed:

  • Setting verify_ssl to False in 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).
Assets 2