7.3.1

[7.3.1] - 2022-02-14

Added:

• CI builds now include a cross-platform test suite implemented in https://github.com/launchdarkly/sdk-test-harness. This covers many test cases that are also implemented in unit tests, but may be extended in the future to ensure consistent behavior across SDKs in other areas.

Fixed:

• The SDK no longer uses the deprecated method threading.Condition.notifyAll(). (Thanks, jdmoldenhauer!)
• A rule clause that uses a date operator should be considered a non-match, rather than an error, if either value is None.
• A rule clause that uses a semver operator should be considered a non-match, rather than an error, if either value is not a string.
• Rules targeting the secondary attribute will now reference the correct value.
• The identify method should not emit an event if the user key is an empty string.
• Do not include prereqOf field in event data if it is null. This is done to save on event transfer bandwidth.
• Data from all_flags_state was always including the flag's version even when it was unnecessary.
• Any base URIs set in Config will work consistently whether they have trailing slashes or not.
• When using all_flags_state to produce bootstrap data for the JavaScript SDK, the Python SDK was not returning the correct metadata for evaluations that involved an experiment. As a result, the analytics events produced by the JavaScript SDK did not correctly reflect experimentation results.
• Data from all_flags_state was always including the flag's version even when it was unnecessary.

7.3.0

[7.3.0] - 2021-12-10

Added:

• The SDK now supports evaluation of Big Segments. See: https://docs.launchdarkly.com/home/users/big-segments

7.2.1

[7.2.1] - 2021-12-03

Changed:

• Added CI testing for Python 3.10.

Fixed:

• In streaming mode, the SDK could sometimes fail to receive flag data from LaunchDarkly if the data contained characters that are not in the Basic Latin character set. The error was intermittent and would depend on unpredictable factors of speed and network behavior which could cause the first byte of a multi-byte UTF8 character to be processed before the rest of the bytes had arrived.
• Fixed some irregularities in the SSE parsing logic used for stream data. The SDK's CI tests now include a more thorough test suite for SSE behavior that is implemented in https://github.com/launchdarkly/sse-contract-tests, to ensure that it is consistent with other LaunchDarkly SDKs.

7.2.0

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

7.1.0

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

6.13.3

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

7.0.2

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

7.0.1

[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!)

7.0.0

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

6.13.2

[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!)