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.0b202611101810

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.0b202611101810
File Size Uploaded Provenance Actions
oai_statsig_python_core-0.41.0b202611101810.tar.gz 2.8 MB With provenance Details for oai_statsig_python_core-0.41.0b202611101810.tar.gz

Built distributions (wheels)

Table of built distributions (wheels) for oai-statsig-python-core 0.41.0b202611101810
File Actions
oai_statsig_python_core-0.41.0b202611101810-cp310-abi3-win_amd64.whl CPython 3.10 abi3 Windows x86-64 Details for oai_statsig_python_core-0.41.0b202611101810-cp310-abi3-win_amd64.whl
oai_statsig_python_core-0.41.0b202611101810-cp310-abi3-win32.whl CPython 3.10 abi3 Windows x86-32 Details for oai_statsig_python_core-0.41.0b202611101810-cp310-abi3-win32.whl
oai_statsig_python_core-0.41.0b202611101810-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.0b202611101810-cp310-abi3-musllinux_1_2_x86_64.whl
oai_statsig_python_core-0.41.0b202611101810-cp310-abi3-musllinux_1_2_aarch64.whl CPython 3.10 abi3 Linux musl 1.2+ ARM64 Details for oai_statsig_python_core-0.41.0b202611101810-cp310-abi3-musllinux_1_2_aarch64.whl
oai_statsig_python_core-0.41.0b202611101810-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.0b202611101810-cp310-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
oai_statsig_python_core-0.41.0b202611101810-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.0b202611101810-cp310-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
oai_statsig_python_core-0.41.0b202611101810-cp310-abi3-macosx_11_0_arm64.whl CPython 3.10 abi3 macOS 11.0+ ARM64 Details for oai_statsig_python_core-0.41.0b202611101810-cp310-abi3-macosx_11_0_arm64.whl
oai_statsig_python_core-0.41.0b202611101810-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.0b202611101810-cp310-abi3-macosx_10_12_x86_64.whl

Total release size: 142.1 MB

Release files / oai_statsig_python_core-0.41.0b202611101810.tar.gz

Download URL oai_statsig_python_core-0.41.0b202611101810.tar.gz
Size 2.8 MB
Tags Source
SHA-256 checksum
How to use checksums
7554bd011aff5f3be4bc2eafa6bd5d2000beb43d9f547b0b15cac729eb527f08
BLAKE2b-256 checksum
How to use checksums
fdf1aecb6176502f2d5498550aae41ff7819a6896f4e1dfe17679045233f6193
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 11, 2026.

Transparency log

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

Download URL oai_statsig_python_core-0.41.0b202611101810-cp310-abi3-win_amd64.whl
Size 7.8 MB
Tags CPython 3.10 Windows x86-64 abi3
SHA-256 checksum
How to use checksums
980be983a1f568220040c90e85106c890adc799eea5358c35c20da58db932aee
BLAKE2b-256 checksum
How to use checksums
7bc29b8ea5c085c66ce0a725b703ef588d4d879f52a8b21da6e3976905bd5d2b
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 11, 2026.

Transparency log

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

Download URL oai_statsig_python_core-0.41.0b202611101810-cp310-abi3-win32.whl
Size 7.0 MB
Tags CPython 3.10 Windows x86-32 abi3
SHA-256 checksum
How to use checksums
862780e6079fc0744dbe89eee2a8c8a2467265d1099e73e4547bef72334dee84
BLAKE2b-256 checksum
How to use checksums
9f1523ce250fa80ecc48fb5758eaab8900d23cee5274af72d5c1ba3bc0d0129e
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 11, 2026.

Transparency log

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

Download URL oai_statsig_python_core-0.41.0b202611101810-cp310-abi3-musllinux_1_2_x86_64.whl
Size 26.8 MB
Tags CPython 3.10 Linux musl 1.2+ x86-64 abi3
SHA-256 checksum
How to use checksums
882ceb2f4782374739afe36dca8fe329976a1179ee93a3ad8f6d51596787bd47
BLAKE2b-256 checksum
How to use checksums
93fcecf6b1617150826ff57f2ad380043449e139c9f1a3308a3a8d02fdbdd318
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 11, 2026.

Transparency log

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

Download URL oai_statsig_python_core-0.41.0b202611101810-cp310-abi3-musllinux_1_2_aarch64.whl
Size 26.5 MB
Tags CPython 3.10 Linux musl 1.2+ ARM64 abi3
SHA-256 checksum
How to use checksums
359f6aba8f14de3ba7b550afa1e2295b6cfa2f427de6a498e9d33d0c1ca9b987
BLAKE2b-256 checksum
How to use checksums
296050b4eed0619fa422af121cdc2969efea7f03a02abe9fab28aec6e8fe09fc
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 11, 2026.

Transparency log

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

Download URL oai_statsig_python_core-0.41.0b202611101810-cp310-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Size 29.8 MB
Tags CPython 3.10 Linux glibc 2.17+ x86-64 abi3
SHA-256 checksum
How to use checksums
3e8e1648b3f5da4bdfe55240005fbc19c681e602782a7cdcde1eb666143163f4
BLAKE2b-256 checksum
How to use checksums
b5eaa4cb02b937820794b24a49087b143d6038f987442607dde5866268426686
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 11, 2026.

Transparency log

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

Download URL oai_statsig_python_core-0.41.0b202611101810-cp310-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
Size 26.0 MB
Tags CPython 3.10 Linux glibc 2.17+ ARM64 abi3
SHA-256 checksum
How to use checksums
f2f13fd440dee478df508cfa27910c59ba4b0cc7d48ffbd815bab2a4b01c82d4
BLAKE2b-256 checksum
How to use checksums
c6c6ca04cc0bccc325c8d71ab0e80eff662a1f1498d3840abdc769f5139e49af
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 11, 2026.

Transparency log

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

Download URL oai_statsig_python_core-0.41.0b202611101810-cp310-abi3-macosx_11_0_arm64.whl
Size 7.6 MB
Tags CPython 3.10 abi3 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
ac7eb55d8c06287cb0ceb10345cd8191873a6bb0552b20a6d815c26431e4a7dc
BLAKE2b-256 checksum
How to use checksums
445b2fb82e03db0354ca060670d039e335dbdb3d5e6f27bd54e42aeb4326cf4c
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 11, 2026.

Transparency log

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

Download URL oai_statsig_python_core-0.41.0b202611101810-cp310-abi3-macosx_10_12_x86_64.whl
Size 7.9 MB
Tags CPython 3.10 abi3 macOS 10.12+ x86-64
SHA-256 checksum
How to use checksums
6b3021751fde71330730e91f4096cd4670c7ed54281aee214c279060647a5a7f
BLAKE2b-256 checksum
How to use checksums
4c41550f5e78df17f9934f18e742a936a62c98ee3852f8d9c58ec814c4ee5bd7
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 11, 2026.

Transparency log

Security for oai-statsig-python-core 0.41.0b202611101810

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.0b202611101810.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 11, 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