Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

Statsig helps you move faster with feature gates (feature flags), and/or dynamic configs. It also allows you to run A/B/n tests to validate your new features and understand their impact on your KPIs. If you're new to Statsig, check out our product and create an account at statsig.com.

Getting Started

Read through the Documentation or check out the Samples.

Development

Use the Node.js version in .node-version for repository tooling and local builds. For example, with nvm:

nvm install "$(cat .node-version)"

This is the repository toolchain version; it does not change the Node.js versions supported by the published SDK.

ID-list file routing and fallback

See ID-list loading for eager and lazy loading semantics, timeouts, concurrency, refresh behavior, and binding support.

download_id_list_file_api selects the preferred base URL for file downloads. Enable fallback_to_statsig_api to try the original file URL from the manifest after an overridden request fails with a retryable network error, provided that URL belongs to the trusted HTTPS OpenAI CDN origin:

let options = statsig_rust::StatsigOptions {
    download_id_list_file_api: Some("http://statsig-proxy:8080".to_string()),
    fallback_to_statsig_api: Some(true),
    ..Default::default()
};

Fallback accepts only https://statsigcdn.openai.com with the default port or explicit :443. Fallback sends no request or SDK credentials to other manifest origins; the original request error is returned. Fallback does not follow redirects. Custom network providers must implement send_without_redirects; otherwise the fallback returns an error without sending a request.

All ID-list file downloads, including direct CDN, proxy, and fallback requests, preserve the URL's path and query except for legacy range parameters, which are removed. Every request sends Range, statsig-id-list-file-size, and Accept-Encoding: identity headers, preserving the file identity and byte offset for incremental updates. Partial responses require a valid Content-Range matching the requested offset and received body length. They may use 206 or, for compatibility, 200. A 200 without Content-Range means the complete available file from byte zero; the SDK applies only bytes after the requested offset. Available bytes may be behind or ahead of the manifest: the SDK advances by bytes actually applied and keeps polling while below the advertised size. Responses that make no progress or have inconsistent ranges use the remaining retry budget without publishing the refresh. Partial bodies without Content-Range are unsupported; a malformed header is rejected even when the status is 200.

Set fallback_to_statsig_api to Some(false) or leave it unset to keep file downloads strictly on the selected destination. There is no fallback attempt when the override resolves to the original URL, no override is set, or the request fails with an authentication rejection (401/403) or another non-retryable error. Response parsing failures do not trigger fallback. This uses the existing option across language bindings; wrappers that disable it continue to opt out.

A successful proxy request makes no additional request. Primary and fallback requests share the same per-file attempt budget (three attempts by default). The next synchronization starts with the configured override again.

GNU/Linux heap trimming

By default, the SDK calls glibc's malloc_trim(0) after eligible config updates and mmap writes. To skip these calls across all SDK instances and native bindings in a process, set NO_MALLOC_TRIM in the worker environment.

export NO_MALLOC_TRIM=1

The SDK checks the variable before each trim. Only 1 and lowercase true skip the call. An unset variable or any other value keeps trimming enabled. For Flink, set the variable in the TaskManager environment and restart the workers so their Python processes inherit it. To restore the default, unset the variable and restart the workers.

Read-only data stores

Rust data stores can override DataStoreTrait::is_read_only(); Python DataStore subclasses can override the synchronous is_read_only() method:

def is_read_only(self) -> bool:
    return not self.is_leader

The default is False, preserving existing writable stores. Return True for a follower that only consumes shared cache entries. Bootstrap/polling reads and config hydration/evaluation remain enabled, but full network responses no longer build or compress hydrated cache snapshots or call the datastore's write methods. Delta responses continue to skip snapshot writes. Keep the role stable during an update. A failing Python capability check is treated as read-only.

Remote SDK telemetry control

Set StatsigOptions.disable_remote_telemetry to Some(true) to suppress Statsig-side diagnostics and SDK exception uploads. ObservabilityClient metrics/errors, local logs, console capture, custom events, and exposures remain active as configured.

Binding Enable suppression
Rust builder StatsigOptions::builder().disable_remote_telemetry(Some(true)).build()
Python StatsigOptions(disable_remote_telemetry=True)
Node { disableRemoteTelemetry: true }
Java new StatsigOptions.Builder().setDisableRemoteTelemetry(true).build()
Go NewOptionsBuilder().WithDisableRemoteTelemetry(true).Build()
C++ options.disable_remote_telemetry = true on StatsigOptionsBuilder
C options JSON {"disable_remote_telemetry": true}

Only boolean true enables suppression; false or unset/null preserves existing reporting. The option is captured per SDK/adapter at construction. Configure it before creating either; roll back by recreating them with false or unset. No process restart is needed. Environment variables and remote config cannot override it, and opposite settings remain isolated even under the same SDK key/instance ID.

Packages

Protobuf-typed reads and publication callbacks are described in Typed dynamic configs, with Python, Node, and Go API guides. See Python mmap preload for optional returnable hash precomputation when loading writer-published artifacts. See Verified blob reuse from mmap for automatic reuse of writer-verified large config values during SDK hydration.

Bindings

Community

If you need any assitance or just have a question, feel free to reach out to us on Slack.

Metadata

Release files for oai-statsig-python-core 0.41.0b202611091810

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for oai-statsig-python-core 0.41.0b202611091810
File Size Uploaded Provenance Actions
oai_statsig_python_core-0.41.0b202611091810.tar.gz 2.7 MB With provenance Details for oai_statsig_python_core-0.41.0b202611091810.tar.gz

Built distributions (wheels)

Table of built distributions (wheels) for oai-statsig-python-core 0.41.0b202611091810
File Actions
oai_statsig_python_core-0.41.0b202611091810-cp310-abi3-win_amd64.whl CPython 3.10 abi3 Windows x86-64 Details for oai_statsig_python_core-0.41.0b202611091810-cp310-abi3-win_amd64.whl
oai_statsig_python_core-0.41.0b202611091810-cp310-abi3-win32.whl CPython 3.10 abi3 Windows x86-32 Details for oai_statsig_python_core-0.41.0b202611091810-cp310-abi3-win32.whl
oai_statsig_python_core-0.41.0b202611091810-cp310-abi3-musllinux_1_2_x86_64.whl CPython 3.10 abi3 Linux musl 1.2+ x86-64 Details for oai_statsig_python_core-0.41.0b202611091810-cp310-abi3-musllinux_1_2_x86_64.whl
oai_statsig_python_core-0.41.0b202611091810-cp310-abi3-musllinux_1_2_aarch64.whl CPython 3.10 abi3 Linux musl 1.2+ ARM64 Details for oai_statsig_python_core-0.41.0b202611091810-cp310-abi3-musllinux_1_2_aarch64.whl
oai_statsig_python_core-0.41.0b202611091810-cp310-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl CPython 3.10 abi3 Linux glibc 2.17+ x86-64 Details for oai_statsig_python_core-0.41.0b202611091810-cp310-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
oai_statsig_python_core-0.41.0b202611091810-cp310-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl CPython 3.10 abi3 Linux glibc 2.17+ ARM64 Details for oai_statsig_python_core-0.41.0b202611091810-cp310-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
oai_statsig_python_core-0.41.0b202611091810-cp310-abi3-macosx_11_0_arm64.whl CPython 3.10 abi3 macOS 11.0+ ARM64 Details for oai_statsig_python_core-0.41.0b202611091810-cp310-abi3-macosx_11_0_arm64.whl
oai_statsig_python_core-0.41.0b202611091810-cp310-abi3-macosx_10_12_x86_64.whl CPython 3.10 abi3 macOS 10.12+ x86-64 Details for oai_statsig_python_core-0.41.0b202611091810-cp310-abi3-macosx_10_12_x86_64.whl

Total release size: 139.6 MB

Release files / oai_statsig_python_core-0.41.0b202611091810.tar.gz

Download URL oai_statsig_python_core-0.41.0b202611091810.tar.gz
Size 2.7 MB
Tags Source
SHA-256 checksum
How to use checksums
77f9ff6f00a312550d92539446bb409814d3a1091aa9e6164a1ff7e0be612da3
BLAKE2b-256 checksum
How to use checksums
cd74f149f8bc892528dc2f620e4bceaa97a9e592e79bb6af1326c24e1160a027
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 10, 2026.

Transparency log

Release files / oai_statsig_python_core-0.41.0b202611091810-cp310-abi3-win_amd64.whl

Download URL oai_statsig_python_core-0.41.0b202611091810-cp310-abi3-win_amd64.whl
Size 7.6 MB
Tags CPython 3.10 Windows x86-64 abi3
SHA-256 checksum
How to use checksums
c6b36152da16b2d41713fd6bf68d8e2f2b856c6b55b1f94cd547b514b1848313
BLAKE2b-256 checksum
How to use checksums
e64323ab8ba8fea1667c31a9afe7b50ca7465aa208720b4b016f51376b050032
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 10, 2026.

Transparency log

Release files / oai_statsig_python_core-0.41.0b202611091810-cp310-abi3-win32.whl

Download URL oai_statsig_python_core-0.41.0b202611091810-cp310-abi3-win32.whl
Size 6.9 MB
Tags CPython 3.10 Windows x86-32 abi3
SHA-256 checksum
How to use checksums
8246b54db9de1974deaac868c01151ff3e181d3a4c72ea1cf35c29298477ef2b
BLAKE2b-256 checksum
How to use checksums
f2a11a30eae830e0ed3c19f5ba5952a106bc783cacd2af86b6849a1a42572655
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 10, 2026.

Transparency log

Release files / oai_statsig_python_core-0.41.0b202611091810-cp310-abi3-musllinux_1_2_x86_64.whl

Download URL oai_statsig_python_core-0.41.0b202611091810-cp310-abi3-musllinux_1_2_x86_64.whl
Size 26.4 MB
Tags CPython 3.10 Linux musl 1.2+ x86-64 abi3
SHA-256 checksum
How to use checksums
bd2fbab61ff0d298e8d3f79e11973ed8c48f91798a7e3f92e41ad67b7c42fce0
BLAKE2b-256 checksum
How to use checksums
4c894eceadff58a3bd3e22e5bf23ce11aa3585f463ff4780e525249ed57dd9d9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 10, 2026.

Transparency log

Release files / oai_statsig_python_core-0.41.0b202611091810-cp310-abi3-musllinux_1_2_aarch64.whl

Download URL oai_statsig_python_core-0.41.0b202611091810-cp310-abi3-musllinux_1_2_aarch64.whl
Size 26.0 MB
Tags CPython 3.10 Linux musl 1.2+ ARM64 abi3
SHA-256 checksum
How to use checksums
0f3a01bf94633e9cea831ac133409ea91122f69b3f636ef901bf26c36b11b50a
BLAKE2b-256 checksum
How to use checksums
eb1733e6e108b0216b6ea98cea3b1d13a574f001309ff78b2e922870c3692b6e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 10, 2026.

Transparency log

Release files / oai_statsig_python_core-0.41.0b202611091810-cp310-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

Download URL oai_statsig_python_core-0.41.0b202611091810-cp310-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Size 29.2 MB
Tags CPython 3.10 Linux glibc 2.17+ x86-64 abi3
SHA-256 checksum
How to use checksums
59c6d60d57c35c279820bceb0cde906b745b65b37ff6ac3957d5349a7fc0b71e
BLAKE2b-256 checksum
How to use checksums
9d9c2d17a86b89b04310fc91c0923af7ef6b8d5ab8d7ebd08e38f01c111b4fd2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 10, 2026.

Transparency log

Release files / oai_statsig_python_core-0.41.0b202611091810-cp310-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl

Download URL oai_statsig_python_core-0.41.0b202611091810-cp310-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
Size 25.5 MB
Tags CPython 3.10 Linux glibc 2.17+ ARM64 abi3
SHA-256 checksum
How to use checksums
026b14fe4aa71c4e9e497ca5c1b071929adf648deb868225db795378cfd36b68
BLAKE2b-256 checksum
How to use checksums
d3d1169673d8786685356ff9b461316e2ea0d921bf34508624700fe535a2ae5a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 10, 2026.

Transparency log

Release files / oai_statsig_python_core-0.41.0b202611091810-cp310-abi3-macosx_11_0_arm64.whl

Download URL oai_statsig_python_core-0.41.0b202611091810-cp310-abi3-macosx_11_0_arm64.whl
Size 7.5 MB
Tags CPython 3.10 abi3 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
b8633174c60c91e30d04d963a4842568108d99332fc31f5da14e773b703abe46
BLAKE2b-256 checksum
How to use checksums
4d2c66542ab5fbcc2c675c66efc3575a170577e28d710c26a445236a06380a3c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 10, 2026.

Transparency log

Release files / oai_statsig_python_core-0.41.0b202611091810-cp310-abi3-macosx_10_12_x86_64.whl

Download URL oai_statsig_python_core-0.41.0b202611091810-cp310-abi3-macosx_10_12_x86_64.whl
Size 7.8 MB
Tags CPython 3.10 abi3 macOS 10.12+ x86-64
SHA-256 checksum
How to use checksums
4fd455943e2d34c6d49bf33e92cb0a111d81dd304af47d2f7efb6fe6028bed75
BLAKE2b-256 checksum
How to use checksums
d970e33b4783cb814fc62f85f7cc1cf47a8c8de3cd991e23b2f2d7a8a73e7824
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 10, 2026.

Transparency log

Security for oai-statsig-python-core 0.41.0b202611091810

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 9 files in this release have been uploaded with provenance metadata.

Select from 9 files

Attestation for oai_statsig_python_core-0.41.0b202611091810.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 10, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page