6.0.2

[6.0.2] - 2018-05-25

Fixed:

• Fixed a bug that caused an error message to be logged (KeyError: 'default') when evaluating a prerequisite flag (and that also prevented an analytics event from being sent for that flag).
• When running in uWSGI, the client will no longer log an error message if the enableThreads option is absent, as long as the threads option has been set to a number greater than 1. (#84)

6.0.0

[6.0.0] - 2018-05-10

Changed:

• To reduce the network bandwidth used for analytics events, feature request events are now sent as counters rather than individual events, and user details are now sent only at intervals rather than in each event. These behaviors can be modified through the LaunchDarkly UI and with the new configuration option inline_users_in_events. For more details, see Analytics Data Stream Reference.
• The analytics event processor now flushes events at a configurable interval defaulting to 5 seconds, like the other SDKs (previously it flushed if no events had been posted for 5 seconds, or if events exceeded a configurable number). This interval is set by the new Config property flush_interval.

Removed:

• Python 2.6 is no longer supported.
• Removed the Config property events_upload_max_batch_size, which is no longer relevant in the new event flushing logic (see above).

5.0.4

[5.0.4] - 2018-04-16

Fixed

• It was not possible to install the SDK with pip 10.0.0. This should work now (thanks, @theholy7!) with the latest pip as well as previous versions.

5.0.3

[5.0.3] - 2018-04-10

Fixed

• Fixed a bug that, in Python 3.x, caused an error when using an integer user attribute to compute a rollout.
• Fixed a bug that, in Python 3.x, made the all_flags method return a dictionary with byte-string keys instead of string keys when using the Redis feature store.

5.0.2

[5.0.2] - 2018-03-27

Fixed

• In the Redis feature store, fixed a synchronization problem that could cause a feature flag update to be missed if several of them happened in rapid succession.

5.0.1

Added

• Support for a new LaunchDarkly feature: reusable user segments.

Changed

• The FeatureStore interface has been changed to support user segment data as well as feature flags. Existing code that uses InMemoryFeatureStore or RedisFeatureStore should work as before, but custom feature store implementations will need to be updated.

Removed

• Twisted is no longer supported.

5.0.0

This release was broken and has been removed.

4.3.0

[4.3.0] - 2018-02-07

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

[4.2.1] - 2018-01-31

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

[4.2.0] - 2018-01-12

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.