---
title: Python-SDK - 3.3.0
slug: feature-experimentation/release-notes/python-sdk-3-3-0
docTags: 
createdAt: 2026-07-20T15:44:37.228Z
---

\## \[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]\([https://github.com/optimizely/python-sdk/blob/3.3.x/optimizely/event/event\_processor.py#L45](https://github.com/optimizely/python-sdk/blob/3.3.x/optimizely/event/event_processor.py#L45)).
\* 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]\([https://github.com/optimizely/python-sdk/pull/217](https://github.com/optimizely/python-sdk/pull/217)))

[https://github.com/optimizely/python-sdk/releases/tag/3.3.0](https://github.com/optimizely/python-sdk/releases/tag/3.3.0)