Be notified of new releases
Create your free GitHub account today to subscribe to this repository for new releases and build software alongside 36 million developers.Sign up
[6.9.2] - 2019-05-01
- Changed the artifact name from
- Changed repository references to use the new URL
There are no other changes in this release. Substituting
ldclient-py version 6.9.1 with
launchdarkly-server-sdk version 6.9.2 will not affect functionality. Be sure to uninstall the
ldclient-py dependency from your runtime environment when making this change.
[6.9.1] - 2019-04-26
set_sdk_keyfunction was comparing the existing SDK key (if any) to the new one by identity (
is) rather than equality (
==). In Python, two strings that have the same characters may or may not be the same string instance; in the case where they were not,
set_sdk_keywould inappropriately reinitialize the client even though the SDK key had not really changed. (Thanks, jpgimenez!)
- Running the SDK unit tests is now simpler in that the database integrations can be skipped. See
Note on future releases
The LaunchDarkly SDK repositories are being renamed for consistency. This repository is now
python-server-sdk rather than
The package name will also change. In the 6.9.1 release, it is still
ldclient-py; in all future releases, it will be
launchdarkly-server-sdk. No further updates to the
ldclient-py package will be published after this release.
[6.9.0] - 2019-04-09
- It is now possible to use the
withstatement on an LDClient object, so that
close()will be called automatically when it goes out of scope.
close()on the client would cause an error if the configuration included
[6.8.4] - 2019-03-29
- Setting user attributes to non-string values when a string was expected would cause analytics events not to be processed. Also, in the case of the "secondary" attribute, this could cause evaluations to fail for a flag with a percentage rollout. The SDK will now convert attribute values to strings as needed. (#115)
identifyis called without a user, the SDK now logs a warning, and does not send an analytics event to LaunchDarkly (since it would not be processed without a user).
[6.8.3] - 2019-02-12
Note that starting with this release, generated API documentation is available online at https://launchdarkly-python-sdk.readthedocs.io. This is published automatically from the documentation comments in the code.
- The SDK no longer uses
- The CI test suite for all supported Python versions, which previously only ran in Linux, has been extended to include Python 3.6 in Windows.
- Corrected and expanded many documentation comments. All public API methods (not including internal implementation details) are now documented.
[6.8.2] - 2019-01-31
- Fixed a different packaging error that was still present in the 6.8.1 release, which made the package installable but caused imports to fail. The 6.8.1 release has been pulled from PyPI. We apologize for these recent errors, which were not detected prior to release because our prerelease testing was using the source code directly rather than installing it with
pip. Our CI tests have been updated and should prevent this in the future.
[6.8.1] - 2019-01-31
- Fixed a packaging error that made the 6.8.0 release not installable. There are no other changes. The 6.8.0 release has been pulled from PyPI.
This release could not be installed due to a packaging error, and has been removed from PyPI.
[6.8.0] - 2019-01-31
- It is now possible to use Consul as a persistent feature store, similar to the existing Redis and DynamoDB integrations. See
ldclient.integrations, and the reference guide for "Using a persistent feature store".
[6.7.0] - 2019-01-15
- It is now possible to use DynamoDB as a persistent feature store, similar to the existing Redis integration. See
ldclient.integrations, and the reference guide to "Using a persistent feature store".
- The new class
ldclient.feature_store) encapsulates all the parameters that control local caching in database feature stores. This takes the place of the
capacityparameters that are in the deprecated
RedisFeatureStoreconstructor; it can be used with DynamoDB and any other database integrations in the future, and if more caching options are added to
CacheConfigthey will be automatically supported in all of the feature stores.
ldclient.redis_feature_store. The recommended way to create a Redis feature store now is to use
[6.6.0] - 2018-11-14
- It is now possible to inject feature flags into the client from local JSON or YAML files, replacing the normal LaunchDarkly connection. This would typically be for testing purposes. See