Vwo-fme-python-sdk

Latest version: v1.62.0

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

Scan your dependencies

Page 1 of 6

1.62.0

Added

- Added support for internal event sampling for `vwo_sdkUsageStats` and high-volume `vwo_sdkDebug` events.

1.61.0

Fixed

- Resolved various bugs including gateway URL issues with `proxy_url`, incorrect experiment/rollout keys in integrations callbacks, and improved error messaging for context validation and event tracking.

1.60.0

Added

- Added support for `campaignVariation` segmentation operator to evaluate web testing campaign assignments. Context can now pass `platformVariables.webTestingCampaigns` (as a JSON object or JSON string) to target users based on their web testing campaign and variation assignments.

1.55.0

Added

- Added support for FE Usage Tracking. The SDK now accurately tracks usage for features by firing a new usage tracking event (`vwo_feTrackUsage`) for storage hits, feature-not-found cases, and cached holdouts etc.

1.50.0

This release introduces **Wingify** as the primary SDK branding and package namespace, while keeping existing **VWO** integrations fully supported.

Added

- **Wingify public API** — use `init`, `WingifyClient`, `WingifyBuilder`, and `WingifyOptionsModel` from the `wingify` package as the recommended entry point for new integrations.

python
from wingify import init

client = init(
{
"account_id": "123456",
"sdk_key": "32-alpha-numeric-sdk-key",
}
)

context = {"id": "user-123"}

flag = client.get_flag("feature-key", context)
print(flag.is_enabled())
print(flag.get_variables())


- Dual-brand support: single codebase builds two PyPI packages — `vwo-fme-python-sdk` (legacy) and `wingify-fme-python-sdk` (new).
- Build script `scripts/build_wheels.sh` to produce both PyPI wheels via `SDK_BRAND` env var; runtime branding via `is_via_vwo` at init.
- Wingify brand uses split hosts: settings on `edge.wingify.net`, events on `collect.wingify.net`.
- Dual support for `_wingify_meta` / `_vwo_meta` and `wingifyBuilder` / `vwoBuilder` option keys.

Changed

- The SDK implementation now lives under the `wingify` package.
- Log messages and documentation have been updated to reflect Wingify branding.
- **No breaking changes for existing integrations** — server event names, payload keys, and runtime behavior remain compatible with the VWO platform.

Deprecated

The following **VWO** types in `vwo` are deprecated but **continue to work without modification**:

| Deprecated (still supported) | Use instead |
|---|---|
| `vwo.init` | `wingify.init` |
| `vwo.VWOClient` | `wingify.WingifyClient` |
| `vwo.VWOBuilder` | `wingify.WingifyBuilder` |
| `vwo.VWOOptionsModel` | `wingify.WingifyOptionsModel` |
| `vwo.StorageConnector` | `wingify.StorageConnector` |
| `vwo.LogLevelEnum` | `wingify.LogLevelEnum` |

Existing code does not need to change immediately. We recommend adopting the Wingify API for new projects and migrating when convenient:

python
Still supported — no action required today
from vwo import init

client = init(
{
"account_id": "123456",
"sdk_key": "32-alpha-numeric-sdk-key",
}
)

context = {"id": "user-123"}

flag = client.get_flag("feature-key", context)


**Migration tip:** Replace imports from `vwo` with `wingify`, and rename types (`VWOClient` → `WingifyClient`, `VWOBuilder` → `WingifyBuilder`, `VWOOptionsModel` → `WingifyOptionsModel`). Method signatures and SDK behavior are unchanged. See [MIGRATE.md](MIGRATE.md) for details.

1.21.1

Fixed

- Fixed polling not detecting settings changes from the server when `poll_interval` is set.

Page 1 of 6

© 2026 Safety CLI Cybersecurity Inc. All Rights Reserved.