Release 3.5.1

[3.5.1] - July 10th, 2020

Bug Fixes:

• Fixed HTTP request exception handling in PollingConfigManager. (#285)

Release 3.5.0

[3.5.0] - July 9th, 2020

New Features:

• Introduced 2 APIs to interact with feature variables:
  • get_feature_variable_json allows you to get value for JSON variables related to a feature.
  • get_all_feature_variables gets values for all variables under a feature.
• Added support for fetching authenticated datafiles. AuthDatafilePollingConfigManager is a new config manager that allows you to poll for a datafile belonging to a secure environment. You can create a client by setting the datafile_access_token.

Bug Fixes:

• Fixed log messages for targeted rollouts evaluation. (#268)

Release 3.4.2

[3.4.2] - June 11th, 2020

Bug Fixes:

• Adjusted log level for audience evaluation logs. (#267).

Release 3.4.1

[3.4.1] - March 19th, 2020

Bug Fixes:

• Updated jsonschema to address installation issue.

Release 3.4.0

[3.4.0] - January 27th, 2020

New Features:

• Added a new API to get project configuration static data.
  • Call get_optimizely_config() to get a snapshot of project configuration static data.
  • It returns an OptimizelyConfig instance which includes a datafile revision number, all experiments, and feature flags mapped by their key values.
  • Added caching for get_optimizely_config() - OptimizelyConfig object will be cached and reused for the lifetime of the datafile.
  • For details, refer to our documentation page: https://docs.developers.optimizely.com/full-stack/docs/optimizelyconfig-python.

Release 3.3.1

[3.3.1] - December 16th, 2019

Bug Fixes:

• Fixed installation issue on Windows. (#224)
• Fixed batch event processor deadline reset issue. (#227)
• Added more batch event processor debug messages. (#228)

Release 3.3.0

[3.3.0] - October 28th, 2019

New Features:

• Added support for event batching via the event processor.
  • Events generated by methods like activate, track, and is_feature_enabled will be held in a queue until the configured batch size is reached, or the configured flush interval has elapsed. Then, they will be batched into a single payload and sent to the event dispatcher.
  • To configure event batching, set the batch_size and flush_interval properties when initializing instance of BatchEventProcessor.
  • Event batching is disabled by default. You can pass in instance of BatchEventProcessor when creating Optimizely instance to enable event batching.
  • Users can subscribe to LogEvent notification to be notified of whenever a payload consisting of a batch of user events is handed off to the event dispatcher to send to Optimizely's backend.
• Introduced blocking timeout in PollingConfigManager. By default, calls to get_config will block for maximum of 10 seconds until config is available.

Bug Fixes:

• Fixed incorrect log message when numeric metric is not used. (#217)

Release 3.2.0

[3.2.0] - August 27th, 2019

New Features:

• Added support for automatic datafile management via PollingConfigManager:
  • The PollingConfigManager is an implementation of the BaseConfigManager.
  • Users may provide one of datafile or SDK key (sdk_key) or both to optimizely.Optimizely. Based on that the SDK will use the StaticConfigManager or the PollingConfigManager. Refer to the README for more instructions.
  • An initial datafile can be provided to the PollingConfigManager to bootstrap before making HTTP requests for the hosted datafile.
  • Requests for the datafile are made in a separate thread and are scheduled with fixed delay.
  • Configuration updates can be subscribed to by adding the Optimizely config notification.
• Introduced Optimizely.get_feature_variable API. (#191)

Deprecated:

• NotificationCenter.clear_notifications is deprecated as of this release. Please use NotificationCenter.clear_notification_listeners. (#182)
• NotificationCenter.clear_all_notifications is deprecated as of this release. Please use NotificationCenter.clear_all_notification_listeners. (#182)

Release 3.2.0-beta.1

[3.2.0b1] - July 26th, 2019

New Features:

• Added support for automatic datafile management via PollingConfigManager:
  • The PollingConfigManager is an implementation of the BaseConfigManager.
  • Users may provide one of datafile or SDK key (sdk_key) or both to optimizely.Optimizely. Based on that the SDK will use the StaticConfigManager or the PollingConfigManager. Refer to the README for more instructions.
  • An initial datafile can be provided to the PollingConfigManager to bootstrap before making HTTP requests for the hosted datafile.
  • Requests for the datafile are made in a separate thread and are scheduled with fixed delay.
  • Configuration updates can be subscribed to by adding the Optimizely config notification.
• Introduced Optimizely.get_feature_variable API. (#191)

Deprecated:

• NotificationCenter.clear_notifications is deprecated as of this release. Please use NotificationCenter.clear_notification_listeners. (#182)
• NotificationCenter.clear_all_notifications is deprecated as of this release. Please use NotificationCenter.clear_all_notification_listeners. (#182)

Release 3.1.0

[3.1.0] - May 3rd, 2019

New Features:

• Introduced Decision notification listener to be able to record:
  • Variation assignments for users activated in an experiment.
  • Feature access for users.
  • Feature variable value for users.

Bug Fixes:

• Feature variable APIs now return default variable value when
  featureEnabled property is false.
  (#171)

Deprecated:

• Activate notification listener is deprecated as of this release.
  Recommendation is to use the new Decision notification listener.
  Activate notification listener will be removed in the next major
  release.