|
1 | 1 | # Optimizely Python SDK Changelog |
2 | 2 |
|
| 3 | +## 4.1.1 |
| 4 | +March 10th, 2023 |
| 5 | + |
| 6 | +We updated our README.md and other non-functional code to reflect that this SDK supports both Optimizely Feature Experimentation and Optimizely Full Stack. ([#420](https://github.com/optimizely/python-sdk/pull/420)) |
| 7 | + |
3 | 8 | ## 4.1.0 |
4 | 9 | July 7th, 2022 |
5 | 10 |
|
@@ -30,10 +35,10 @@ January 12th, 2022 |
30 | 35 | September 16th, 2021 |
31 | 36 |
|
32 | 37 | ### New Features |
33 | | -* Added new public properties to OptimizelyConfig. |
| 38 | +* Added new public properties to OptimizelyConfig. |
34 | 39 | - sdk_key and environment_key [#338] (https://github.com/optimizely/python-sdk/pull/338) |
35 | 40 | - attributes and events [#339] (https://github.com/optimizely/python-sdk/pull/339) |
36 | | - - experiment_rules, delivery_rules, audiences and audiences in OptimizelyExperiment |
| 41 | + - experiment_rules, delivery_rules, audiences and audiences in OptimizelyExperiment |
37 | 42 | - [#342] (https://github.com/optimizely/python-sdk/pull/342) |
38 | 43 | - [#351] (https://github.com/optimizely/python-sdk/pull/351/files) |
39 | 44 | * For details please refer to our documentation page: |
@@ -158,7 +163,7 @@ October 28th, 2019 |
158 | 163 | * To configure event batching, set the `batch_size` and `flush_interval` properties when initializing instance of [BatchEventProcessor](https://github.com/optimizely/python-sdk/blob/3.3.x/optimizely/event/event_processor.py#L45). |
159 | 164 | * Event batching is disabled by default. You can pass in instance of `BatchEventProcessor` when creating `Optimizely` instance to enable event batching. |
160 | 165 | * 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. |
161 | | -* Introduced blocking timeout in `PollingConfigManager`. By default, calls to `get_config` will block for maximum of 10 seconds until config is available. |
| 166 | +* Introduced blocking timeout in `PollingConfigManager`. By default, calls to `get_config` will block for maximum of 10 seconds until config is available. |
162 | 167 |
|
163 | 168 | ### Bug Fixes: |
164 | 169 | * Fixed incorrect log message when numeric metric is not used. ([#217](https://github.com/optimizely/python-sdk/pull/217)) |
|
0 commit comments