Launchdarkly-server-sdk

Latest version: v9.4.0

Safety actively analyzes 638730 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 13 of 15

4.3.0

Changed
- Percentage rollouts can now reference an attribute with an integer value, not just string attributes.

Fixed
- Fixed a bug that caused unusually slow initialization times when there are large numbers of flags.
- Fixed reporting of events for prerequisite checks.

4.2.1

Changed
- Reduced WARN-level logging for a feature flag not being found to INFO level.

Fixed
- Fixed a bug where a previously deleted feature flag might be considered still available.
- The private attributes feature added in v4.1.0 was not available in Twisted mode; now it is.

4.2.0

Changed
- Will use feature store if already initialized even if connection to service could not be established. This is useful when flags have been initialized in redis.

4.1.0

Added
- Allow user to stop user attributes from being sent in analytics events back to LaunchDarkly. Set `private_attribute_names` on each
request and/or on `Config` to a list of strings matching the names of the attributes you wish to exclude. Set
`all_attributes_private` on the `Config` object to hide all attributes.

Changed
- Stop reattempting connections when receiving a 401 (unauthorized) response from LaunchDarkly. This should only be caused by invalid SDK key so retrying is pointless.

Deprecated
- `events_enabled` is deprecated and `send_events` should be used instead. `events_enabled` may be removed in a future minor revision.

4.0.6

Changed
- Improved error handling when processing stream events
- Replaced 3rd party rfc3339 library for license compliance
- No longer caching `get_one()` responses

4.0.5

Fixed
- [70](https://github.com/launchdarkly/python-client/issues/70) Regex `matches` targeting rules now include the user if
a match is found anywhere in the attribute. Before fixing this bug, the beginning of the attribute needed to match the pattern.
Changed
- [43](https://github.com/launchdarkly/python-client/issues/43) Started publishing code coverage metrics to Code Climate.
Bear in mind that the Code Climate coverage report only shows the unit test coverage, while the bulk of our SDK test coverage comes
from a [separate integration test suite](https://github.com/launchdarkly/python-client#testing).

Page 13 of 15

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.