RocketFlag Python SDK
Official Python SDK for RocketFlag. Same evaluation API as the Node and Go SDKs: create a client, fetch a flag, branch on flag.enabled.
Beta: the evaluation API matches Node and Go, but packaging and docs may still change. Prefer pinning a version in production.
Installation
pip install rocketflag
Python 3.9+. No third-party runtime dependencies.
Published releases go to PyPI via GitHub Releases. For an unreleased commit:
pip install git+https://github.com/RocketFlag/python-sdk.git
Basic usage
from rocketflag import create_client
rocketflag = create_client() # default API URL and version (v1)
flag = rocketflag.get_flag("IFldMzqP5jtv9wAL")
if flag.enabled:
render_new_dashboard()
else:
render_legacy_dashboard()
You can also construct Client directly:
from rocketflag import Client
client = Client()
flag = client.get_flag("IFldMzqP5jtv9wAL")
Custom version or API URL
rocketflag = create_client("v2", "https://your-api-domain.com")
Cohorts and environment
flag = rocketflag.get_flag("IFldMzqP5jtv9wAL", {
"cohort": "beta",
"env": "prod",
})
env selects the environment of a group flag. Environment names contain letters, numbers, hyphens and underscores.
Sticky rollouts and audiences
Pass a targetingKey to make percentage rollouts sticky, and any other keys as audience attributes:
flag = rocketflag.get_flag("IFldMzqP5jtv9wAL", {
"targetingKey": user.id,
"plan": "pro",
"country": "AU",
})
targetingKey: a stable identifier for the user. The same key always gets the same answer from a percentage rollout, in every environment of a group flag, and raising the percentage only ever adds users. Without atargetingKeythecohortis used, and with neither each request is a fresh random roll. Prefer an opaque id over an email address: the key is part of the request URL.- Any other key is an audience attribute, matched against the flag's audience exactly and case-sensitively. An attribute you don't send never matches.
cohort,envandtargetingKeyare reserved and can't be audience attributes.
Context values must be str, int, float or bool. None raises ValueError, so leave out an attribute you don't have. The UserContext type hint excludes None too, so a type checker catches it first.
Caching
Opt-in in-memory cache, keyed by flag ID and user context. Same behaviour as Node/Go.
# Cache flag responses for 5 minutes.
rocketflag = create_client(ttl_seconds=300)
flag = rocketflag.get_flag("IFldMzqP5jtv9wAL", {"cohort": "beta"})
# Force a fresh fetch.
flag = rocketflag.get_flag("IFldMzqP5jtv9wAL", ttl_seconds=0)
# Shorter TTL for one call.
flag = rocketflag.get_flag("IFldMzqP5jtv9wAL", ttl_seconds=10)
Without a client default or per-call TTL, every call hits the API. Each distinct context is its own cache entry, so a targetingKey per user means an entry per user. The cache holds at most 10,000 entries and evicts the least recently used one when it is full. Change the cap with max_entries:
rocketflag = create_client(ttl_seconds=300, max_entries=50_000)
Errors
from rocketflag import APIError, InvalidResponseError, NetworkError, create_client
rocketflag = create_client()
try:
flag = rocketflag.get_flag("IFldMzqP5jtv9wAL")
except APIError as err:
print(f"API Error: {err.status} {err.status_text}")
except InvalidResponseError as err:
print(f"Invalid Response Error: {err}")
except NetworkError as err:
print(f"Network Error: {err}")
APIError— non-OK HTTP status (includesstatus/status_text). A404means the flag ID is unknown.InvalidResponseError— body is not JSON or not a flag object (name,enabled,id).NetworkError— connection failure.
Response
A successful call returns a Flag:
Flag(name="The user-created flag name", enabled=True, id="asklWQQZdslhfsszZWkj")
The HTTP API may also return:
200with that object404— flag ID not found500— rare server error; RocketFlag is alerted
Development
python -m pip install -e ".[dev]"
python -m pytest
A container demo that hits the live API lives in demo/.
Metadata
Release files for rocketflag 0.2.0
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 | Actions |
|---|---|---|---|---|
| rocketflag-0.2.0.tar.gz | 10.5 kB | With provenance | Details for rocketflag-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rocketflag-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for rocketflag-0.2.0-py3-none-any.whl |
Total release size: 18.1 kB
Release files / rocketflag-0.2.0.tar.gz
| Download URL | rocketflag-0.2.0.tar.gz |
|---|---|
| Size | 10.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
537a47a1a57206a6592b1ccb72f55496fd1b92fa9ac68e447deade621c8c0cb1
|
|
BLAKE2b-256 checksum How to use checksums |
490ac97d0828d9240e720bb2c167168ab293b5441685084738eeb03785ee0aeb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 5, 2026.
Transparency logRelease files / rocketflag-0.2.0-py3-none-any.whl
| Download URL | rocketflag-0.2.0-py3-none-any.whl |
|---|---|
| Size | 7.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
77d5ba659c349245de9bff84cdf1fbe9586cd16690278dbbe5e715e6d5db8076
|
|
BLAKE2b-256 checksum How to use checksums |
d722cb8909f6513b2dc1c2cedc0af1a16255371fc5c5f60a12b1812ba2ef08fe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 5, 2026.
Transparency logSecurity for rocketflag 0.2.0
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 2 files in this release have been uploaded with provenance metadata.
Attestation for rocketflag-0.2.0.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 5, 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.