Skip to content

Conversation

eli-darkly
Copy link
Contributor

[6.9.1] - 2019-04-26

Fixed:

  • The set_sdk_key function 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_key would 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 CONTRIBUTING.md.

Note on future releases

The LaunchDarkly SDK repositories are being renamed for consistency. This repository is now python-server-sdk rather than python-client.

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.

eli-darkly and others added 30 commits October 4, 2018 19:17
add option to reduce front-end metadata for untracked flags
fix logic for whether a flag is tracked in all_flags_state
hroederld and others added 24 commits March 1, 2019 16:40
don't load test dependencies in Python 3.3 that don't work in Python 3.3
coerce user attributes into strings when necessary, don't send events without valid users
ensure that client components are cleaned up correctly in every configuration
allow unit tests to be run without databases
@eli-darkly eli-darkly merged commit 0884d2e into master Apr 26, 2019
@eli-darkly eli-darkly deleted the 6.9.1 branch April 26, 2019 20:13
LaunchDarklyCI pushed a commit that referenced this pull request Dec 9, 2019
use yaml.safe_load() to avoid code execution vulnerability in file data source
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants