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.
ID-list file routing and fallback
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.
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.
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.
Bindings
Community
If you need any assitance or just have a question, feel free to reach out to us on Slack.
3 maintainers
Metadata
3 maintainers
Release files for oai-statsig-python-core 0.37.0rc2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| oai_statsig_python_core-0.37.0rc2.tar.gz | 2.5 MB | With provenance | Details |
Built distributions (wheels)
Total release size: 129.5 MB
Release files / oai_statsig_python_core-0.37.0rc2.tar.gz
| Download URL | oai_statsig_python_core-0.37.0rc2.tar.gz |
|---|---|
| Size | 2.5 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0b154307e8b9f25d816bf202b54f6b1f8638ae6cae443a22d97ec4655dca876c
|
|
BLAKE2b-256 checksum How to use checksums |
c267b1c2d0413e937d9a74193bfbad504fb3471208b428f7d4f37b558bda763f
|
| 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 Oct 21, 2026.
Transparency logRelease files / oai_statsig_python_core-0.37.0rc2-cp310-abi3-win_amd64.whl
| Download URL | oai_statsig_python_core-0.37.0rc2-cp310-abi3-win_amd64.whl |
|---|---|
| Size | 7.1 MB |
| Tags | CPython 3.10 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
bf7700e4e0dd28fc303e875d13a7d42fd73341e284df04aee2966c7ec0cea58d
|
|
BLAKE2b-256 checksum How to use checksums |
1b897ac463b898a93e3bd268f0296420ed2ae149d742d35630652c0eb6f687dd
|
| 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 Oct 21, 2026.
Transparency logRelease files / oai_statsig_python_core-0.37.0rc2-cp310-abi3-win32.whl
| Download URL | oai_statsig_python_core-0.37.0rc2-cp310-abi3-win32.whl |
|---|---|
| Size | 6.4 MB |
| Tags | CPython 3.10 Windows x86-32 abi3 |
|
SHA-256 checksum How to use checksums |
4b99e6befef4c3e5d4e371d0c775053dc7c7287dea74fc5d5e6a2602b605aff2
|
|
BLAKE2b-256 checksum How to use checksums |
e48dcd8dd601930bb2e274b9480640fdd5fffe4012a5f25e34eff940f5ebd049
|
| 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 Oct 21, 2026.
Transparency logRelease files / oai_statsig_python_core-0.37.0rc2-cp310-abi3-musllinux_1_2_x86_64.whl
| Download URL | oai_statsig_python_core-0.37.0rc2-cp310-abi3-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 24.5 MB |
| Tags | CPython 3.10 Linux musl 1.2+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
161ea3b51c27d1348f650625be85fa6b28c3ed200cdda2e0d4c9c9c832810bab
|
|
BLAKE2b-256 checksum How to use checksums |
4ba26588e5c0261c9ea46a4a47e8fa61b5e84a6bbf9edcb1cc8d87ef400d396d
|
| 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 Oct 21, 2026.
Transparency logRelease files / oai_statsig_python_core-0.37.0rc2-cp310-abi3-musllinux_1_2_aarch64.whl
| Download URL | oai_statsig_python_core-0.37.0rc2-cp310-abi3-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 24.1 MB |
| Tags | CPython 3.10 Linux musl 1.2+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
659016c77aecc56cff067422c82ae47feddfdca1b606b63db6df7c1435613bb0
|
|
BLAKE2b-256 checksum How to use checksums |
4a21a243ada5bbcd64fbe4246f473255932e9bf9511fe6331c08856a2a3e4161
|
| 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 Oct 21, 2026.
Transparency logRelease files / oai_statsig_python_core-0.37.0rc2-cp310-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | oai_statsig_python_core-0.37.0rc2-cp310-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 27.0 MB |
| Tags | CPython 3.10 Linux glibc 2.17+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
73f80564f41ccedbcf8af8546d4392ceb2b38b71a2aaaf86259293870bdd8e21
|
|
BLAKE2b-256 checksum How to use checksums |
cc325235aa8a5548e0dc626c63a1a5e99e44f5156ded0159549d13ffdec12c92
|
| 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 Oct 21, 2026.
Transparency logRelease files / oai_statsig_python_core-0.37.0rc2-cp310-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | oai_statsig_python_core-0.37.0rc2-cp310-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 23.6 MB |
| Tags | CPython 3.10 Linux glibc 2.17+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
15b177e5b1565668cf164bc7452beddadfc55d4d53cd5b81093a9121afd002ec
|
|
BLAKE2b-256 checksum How to use checksums |
d50e996d6c86e0cda432fb374cd8f14cdf9a5578b3be375f327933c62f622e6e
|
| 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 Oct 21, 2026.
Transparency logRelease files / oai_statsig_python_core-0.37.0rc2-cp310-abi3-macosx_11_0_arm64.whl
| Download URL | oai_statsig_python_core-0.37.0rc2-cp310-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 7.0 MB |
| Tags | CPython 3.10 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
5de38b51fc7136d71e751d5b3df23974da79eef1da0b205b3ef3c2751d3d2524
|
|
BLAKE2b-256 checksum How to use checksums |
3fdf7be2a63fce856bcbd843937203c9f5b9566a497f4856be0b79da7b309dd9
|
| 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 Oct 21, 2026.
Transparency logRelease files / oai_statsig_python_core-0.37.0rc2-cp310-abi3-macosx_10_12_x86_64.whl
| Download URL | oai_statsig_python_core-0.37.0rc2-cp310-abi3-macosx_10_12_x86_64.whl |
|---|---|
| Size | 7.3 MB |
| Tags | CPython 3.10 abi3 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
b8464888137f8795770ca294f0985282d2bfde714523b7f0b1c63606e6994e09
|
|
BLAKE2b-256 checksum How to use checksums |
4696e6989dae07ccc83bc1640120d803e6e67f5302ed8da0650f33a8c5788a4a
|
| 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 Oct 21, 2026.
Transparency logSecurity for oai-statsig-python-core 0.37.0rc2
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.
Attestation for oai_statsig_python_core-0.37.0rc2.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 Oct 21, 2026.
Transparency logA 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.
