Steely
A Python debugging and analysis toolkit with beautiful, colorful terminal output.
Steely provides powerful decorators that help developers understand their code's behavior at runtime through automatic logging, execution timing, and real-time variable tracking.
Features
- Dan.log - Automatic function logging with start/success/error tracking
- Dan.cronos - Execution time measurement and profiling
- Dan.scan - Real-time variable tracking with type-colored output
- Logger - Flexible, thread-safe logging with color-coded output and file support
- Logger.getLogger() - Named logger registry with hierarchical level filtering (compatible with
loggingconstants) - Grafana Cloud - Non-blocking background sink for Grafana Cloud (OTLP) and self-hosted Loki
- Email Providers - Send email over SMTP or HTTP APIs (Resend, Mailchimp/SendGrid/… via a generic provider) behind one interface
- Streaming STT - Speech-to-text over Deepgram, AssemblyAI, Google/Chirp, Azure, Amazon Transcribe, or self-hosted WhisperLive behind one async interface
- pprint - Pretty print with caller location information for easy debugging
- FastAPI Integration - Record API requests as Postman collections or curl commands
Everything above ships in a single package. The core (decorators, Logger, Grafana sink, SMTP email) has no required third-party dependencies — it runs on the standard library. HTTP email and each STT backend are opt-in extras so you only install what you use.
Table of Contents
- Installation · Requirements · Quick Start
- Decorators:
Dan.log·Dan.cronos·Dan.scan - Logger · Grafana Integration
- Email Providers · Streaming STT
- pprint · FastAPI Integration
- Advanced Usage · Framework Compatibility
- Deep-dive guides:
EMAIL_PROVIDERS.md·STT_PROVIDERS.md·CHANGELOG.md
Installation
Using pip
pip install steely
Using uv
uv add steely
From source
git clone https://github.com/your-username/steely.git
cd steely
pip install -e .
Optional extras
The core is dependency-light; each integration that needs a third-party SDK is an opt-in extra. Install only what you use:
| Extra | Install | Enables |
|---|---|---|
| (none) | pip install steely |
Decorators, Logger, Grafana sink, SMTP email |
http |
pip install "steely[http]" |
Resend + generic HTTP-API email providers (httpx) |
stt-deepgram |
pip install "steely[stt-deepgram]" |
Deepgram streaming STT |
stt-assemblyai |
pip install "steely[stt-assemblyai]" |
AssemblyAI streaming STT |
stt-google |
pip install "steely[stt-google]" |
Google Cloud / Chirp streaming STT |
stt-azure |
pip install "steely[stt-azure]" |
Azure AI Speech streaming STT |
stt-aws |
pip install "steely[stt-aws]" |
Amazon Transcribe streaming STT |
stt-whisperlive |
pip install "steely[stt-whisperlive]" |
Self-hosted WhisperLive (websockets) |
audio |
pip install "steely[audio]" |
Audio resampling back-port for Python 3.13+ |
stt-all |
pip install "steely[stt-all]" |
Every STT backend |
all |
pip install "steely[all]" |
Every optional integration |
Each backend's SDK is imported lazily, so import steely.stt (or steely.email)
never fails when an extra is absent — only constructing a provider you haven't
installed raises a loud, explicit error at construction time.
Requirements
- Python 3.9 or higher
- No required third-party dependencies for the core — decorators,
Logger, the Grafana sink and SMTP email all run on the standard library alone. HTTP email and the STT backends pull their SDKs only when you install the matching extra.
Quick Start
from steely import Dan
from steely.pprint import pprint
from steely.logger import Logger
# Log function execution
@Dan.log
def fetch_data(url):
return {"data": "example"}
# Measure execution time
@Dan.cronos
def slow_operation():
import time
time.sleep(1)
return "done"
# Track variables in real-time
@Dan.scan
def calculate(a, b):
total = a + b
squared = total ** 2
return squared
# Pretty print with location info
def debug_function(x, y):
result = x + y
pprint(f"Result is: {result}")
return result
# Set global app name for consistent logging
Logger.set_global_app_name("MyApp")
# Run the functions
fetch_data("https://api.example.com")
slow_operation()
calculate(3, 4)
debug_function(10, 20)
FastAPI Quick Start
from fastapi import FastAPI
from steely.fastapi import recorder
app = FastAPI()
# Automatically record requests as Postman collections
@app.get("/users/{user_id}")
@recorder.postman()
async def get_user(user_id: int):
return {"user_id": user_id, "name": "John"}
# Also generate curl commands for testing
@app.post("/users")
@recorder.curl()
async def create_user(name: str):
return {"id": 123, "name": name}
Decorators
Dan.log
The log decorator automatically tracks function execution lifecycle - when it starts, succeeds, or fails.
from steely import Dan
@Dan.log
def process_user(user_id):
# Your code here
return {"id": user_id, "status": "processed"}
process_user(123)
Output:
[PROCESS_USER] [START]: Function called
[PROCESS_USER] [SUCCESS]: Function completed
With async functions
@Dan.log
async def fetch_api_data(endpoint):
async with aiohttp.ClientSession() as session:
async with session.get(endpoint) as response:
return await response.json()
Error tracking
When an exception occurs, the decorator logs the error before re-raising it:
@Dan.log
def risky_operation():
raise ValueError("Something went wrong")
risky_operation()
# Output:
# [RISKY_OPERATION] [START]: Function called
# [RISKY_OPERATION] [ERROR]: Something went wrong
# Traceback...
Dan.cronos
Named after the Greek god of time, cronos measures and reports function execution time.
from steely import Dan
import time
@Dan.cronos
def compute_heavy_task(n):
time.sleep(n)
return sum(range(n * 1000000))
compute_heavy_task(2)
Output:
[*-CRONOS-*] [COMPUTE_HEAVY_TASK] [TEST-RESULT]: Total Time Elapsed: 0:00:02.001234
With async functions
import asyncio
@Dan.cronos
async def async_task():
await asyncio.sleep(0.5)
return "completed"
asyncio.run(async_task())
# Output: Total Time Elapsed: 0:00:00.500xxx
Dan.scan
The scan decorator provides real-time variable tracking with beautiful, type-colored output. It shows every variable assignment, its type, value, and the line number where it was set.
from steely import Dan
@Dan.scan
def example(x, y):
name = "Alice"
numbers = [1, 2, 3]
total = x + y
data = {"key": "value"}
return total
example(10, 20)
Output:
┌─────────────────────────────────────────────────────────────────────────────────────
│ ⚡ SCAN: example
│ module: __main__
├─────────────────────────────────────────────────────────────────────────────────────
│ Parameters:
│ ◈ x: int → 10
│ ◈ y: int → 20
├─────────────────────────────────────────────────────────────────────────────────────
│ Variables:
│ ▸ line 4 ◈ name ◉ str → 'Alice'
│ ▸ line 5 ◈ numbers ◉ list → [1, 2, 3]
│ ▸ line 6 ◈ total ◉ int → 30
│ ▸ line 7 ◈ data ◉ dict → {'key': 'value'}
├─────────────────────────────────────────────────────────────────────────────────────
│ ⟼ Return: int → 30
└───────────────────────────────────────────────────────────── elapsed: 0.12ms ──────
Type Colors
Each Python type is displayed in a distinct color for easy visual identification:
| Type | Color |
|---|---|
int |
Blue |
float |
Deep Blue |
str |
Orange |
bool |
Magenta |
None |
Gray |
list |
Sea Green |
dict |
Gold |
tuple |
Light Purple |
set |
Pink |
callable |
Cyan |
class |
Lavender |
Async Functions
For async functions, variable tracking is disabled (due to event loop tracing limitations), but parameters and return values are still displayed:
@Dan.scan
async def fetch_data(url):
response = await some_api_call(url)
return response
await fetch_data("https://api.example.com")
Combining Decorators
You can stack multiple decorators to get combined functionality:
from steely import Dan
@Dan.log
@Dan.cronos
@Dan.scan
def important_operation(data):
processed = data.upper()
result = len(processed)
return result
important_operation("hello world")
This will:
- Log the function start/success
- Measure execution time
- Track all variable assignments
Logger
The Logger class provides a flexible, thread-safe logging system with color-coded terminal output and optional file logging.
Basic Usage
from steely.logger import Logger
# Create a logger instance
logger = Logger("MyApp", "database")
# Log messages with different levels
logger.info("Connected to database")
logger.success("Query executed successfully")
logger.warning("Connection pool running low")
logger.error("Query timeout after 30s")
Output:
25-11-2025 14:30:00 - [MYAPP] [DATABASE] [INFO]: Connected to database
25-11-2025 14:30:00 - [MYAPP] [DATABASE] [SUCCESS]: Query executed successfully
25-11-2025 14:30:01 - [MYAPP] [DATABASE] [WARNING]: Connection pool running low
25-11-2025 14:30:02 - [MYAPP] [DATABASE] [ERROR]: Query timeout after 30s
Log Levels
| Level | Color | Method | Use Case |
|---|---|---|---|
INFO |
Cyan | logger.info() |
General information |
START |
Cyan | logger.start() |
Process initialization |
SUCCESS |
Green | logger.success() |
Successful operations |
OK |
Green | logger.ok() |
Confirmations |
WARNING |
Yellow | logger.warning() |
Warning messages |
ALERT |
Yellow | logger.alert() |
Alert notifications |
ERROR |
Red | logger.error() |
Error messages |
CRITICAL |
Red | logger.critical() |
Critical errors |
FATAL |
Red | logger.fatal() |
Fatal errors |
FAIL |
Red | logger.fail() |
Failed operations |
FAULT |
Red | logger.fault() |
System faults |
TEST |
Blue | logger.test() |
Test messages |
TEST-RESULT |
Blue | logger.test_result() |
Test results |
File Logging
Enable file logging by providing a destination directory:
from steely.logger import Logger
# Logs will be saved to /var/log/myapp/DD-MM-YYYY.log
logger = Logger("MyApp", "api", destination="/var/log/myapp")
logger.info("Request received") # Printed AND saved to file
logger.error("Request failed") # Printed AND saved to file
Log files are automatically named with the current date (e.g., 25-11-2025.log) and appended throughout the day.
Additional Tags
Add custom tags to your log messages for better filtering:
from steely.logger import Logger
# Tags defined at creation apply to all messages
logger = Logger("MyApp", "auth", session_id="abc123", user_id="42")
logger.info("User logged in")
# Output: [MYAPP] [AUTH] [ABC123] [42] [INFO]: User logged in
# Or add tags per-message
logger.info("Action performed", request_id="req-789")
# Output: [MYAPP] [AUTH] [ABC123] [42] [REQ-789] [INFO]: Action performed
Using log() Method Directly
For dynamic log levels, use the log() method:
from steely.logger import Logger
logger = Logger("MyApp", "main")
# Using log() with any level
logger.log("INFO", "Application started")
logger.log("SUCCESS", "Initialization complete")
logger.log("ERROR", "Connection failed")
# Logger instances are callable
logger("WARNING", "This also works!")
Setting Global App Name
Use set_global_app_name() to set a global application name for all @log decorated functions:
from steely.logger import Logger
from steely import Dan
# Set global app name once
Logger.set_global_app_name("MyApp")
# All @log decorated functions will now use "MyApp" instead of module name
@Dan.log
def process_data():
return "processed"
@Dan.log
def fetch_api():
return "fetched"
# Both functions will log with [MYAPP] prefix
process_data() # Logs: [MYAPP] [PROCESS_DATA] [START]: Function Execution Started...
fetch_api() # Logs: [MYAPP] [FETCH_API] [START]: Function Execution Started...
This is particularly useful for applications where you want consistent app naming across all logged functions without specifying it for each logger instance.
Named Loggers and Level Filtering
Use Logger.getLogger(name) to get or create a named logger instance — identical instances are returned for the same name, so it's safe to call from multiple modules.
import logging # for the standard numeric constants
from steely.logger import Logger
# Get-or-create by name (cached)
log = Logger.getLogger("src.infrastructure")
log.info("database ready")
Filtering by level
log = Logger.getLogger("src.infrastructure")
log.setLevel("WARNING") # string form
log.setLevel(logging.INFO) # int form — fully compatible with logging module
log.info("this is filtered out") # INFO (20) < WARNING (30)
log.warning("this passes") # WARNING (30) >= WARNING (30)
Supported level strings and their numeric equivalents:
| String | Numeric | Includes |
|---|---|---|
"TEST" / "TEST-RESULT" |
10 | test output only |
"INFO" / "START" / "SUCCESS" / "OK" |
20 | info and above |
"WARNING" / "ALERT" |
30 | warnings and above |
"ERROR" / "FAULT" / "FAIL" |
40 | errors and above |
"CRITICAL" / "FATAL" |
50 | critical only |
Pass None to clear a level and fall back to parent/global: log.setLevel(None).
Hierarchical inheritance
Loggers with dotted names inherit the level of the nearest named ancestor.
Logger.getLogger("src").setLevel("WARNING")
# "src.db" has no level of its own → inherits "WARNING" from "src"
Logger.getLogger("src.db").info("filtered") # suppressed
Logger.getLogger("src.db").warning("shown") # passes
# Override for one child only
Logger.getLogger("src.db").setLevel("INFO")
Logger.getLogger("src.db").info("now shown") # passes
Global level
Set a baseline level that applies to all loggers without their own (or an ancestor's) level:
Logger.set_global_level("INFO") # suppress TEST output globally
Logger.set_global_level(0) # reset — log everything (default)
Intercepting Standard Library Logging
Any library that uses Python's standard logging.getLogger(...) — uvicorn, SQLAlchemy, httpx, requests, urllib3, etc. — can have its output captured, re-formatted and routed through Steely's Logger with a single call. No changes needed in the third-party library.
Quick Start — Uvicorn
from steely.logger import Logger
Logger.set_global_app_name("MyAPI")
# Intercept specific loggers
Logger.intercept_stdlib(["uvicorn", "uvicorn.error", "uvicorn.access"])
# Or intercept everything at once (root logger):
Logger.intercept_stdlib()
After the call, every log line from those libraries is displayed with Steely's colouring, file/destination output, and Grafana shipping — exactly as if it were a native Logger call.
Level mapping
| stdlib constant | stdlib value | Steely level |
|---|---|---|
NOTSET |
0 | TEST |
DEBUG |
10 | TEST |
INFO |
20 | INFO |
WARNING |
30 | WARNING |
ERROR |
40 | ERROR |
CRITICAL |
50 | CRITICAL |
How it works
app_nameis required. Set it globally viaLogger.set_global_app_name("MyAPI")or pass it directly:Logger.intercept_stdlib(app_name="MyAPI"). If neither is provided,intercept_stdlibraises a clearValueError.owneris inferred dynamically fromLogRecord.name(e.g."uvicorn.error"becomes the Steely ownerUVICORN.ERROR). If the logger is the root logger (no name), the fallback isrecord.module.- Caller context is appended as tags:
file(pathname),line(line number),func(function name). These appear in the output as[.../path/to/file.py] [42] [FUNC_NAME], consistent with Steely's existing tag system. - Exceptions are fully captured — when a
LogRecordcarriesexc_info, the full traceback is formatted and appended to the message.
Filtering by level
Because intercepted logs pass through Logger.getLogger(owner), you can use setLevel() and hierarchical inheritance on them:
Logger.set_global_app_name("MyAPI")
# Intercept uvicorn
Logger.intercept_stdlib(["uvicorn", "uvicorn.error"])
# Suppress uvicorn.access without filtering the others
Logger.getLogger("uvicorn.access").setLevel("WARNING")
# Or raise the bar for the whole uvicorn family
Logger.getLogger("uvicorn").setLevel("ERROR") # children inherit
Scoping
| Call | Catches |
|---|---|
Logger.intercept_stdlib() |
Everything — every stdlib log message (root logger). |
Logger.intercept_stdlib(["uvicorn"]) |
Only the named loggers and their children (via propagation). |
The root-logger approach is simpler but captures all third-party output. The named-logger approach is more selective; each named logger gets propagate=False to avoid double emission.
Idempotency
Calling intercept_stdlib multiple times is safe — handlers are never duplicated. If you call it once with root and again with a named list, the named loggers also get propagate=False so no line appears twice.
Screen Clearing
Enable screen clearing for a cleaner terminal experience:
from steely.logger import Logger
# Clear screen before each log message
logger = Logger("MyApp", "installer", clean=True)
logger.info("Step 1: Downloading...") # Clears screen, then prints
logger.info("Step 2: Installing...") # Clears screen, then prints
logger.success("Installation complete!")
Debug Mode
Control debug output with the debug parameter:
from steely.logger import Logger
# Debug mode enabled (default) - appends "_debug" to log directory
logger = Logger("MyApp", "main", destination="/logs", debug=True)
# Logs go to: /logs_debug/DD-MM-YYYY.log
# Production mode
logger = Logger("MyApp", "main", destination="/logs", debug=False)
# Logs go to: /logs/DD-MM-YYYY.log
Thread Safety
All logging operations run in separate threads for non-blocking behavior:
from steely.logger import Logger
import time
logger = Logger("MyApp", "worker")
def process_items(items):
for item in items:
logger.info(f"Processing {item}") # Non-blocking
# Heavy processing here...
time.sleep(0.1)
logger.success("All items processed")
# Logging won't slow down your processing
process_items(["item1", "item2", "item3"])
Complete Example
from steely.logger import Logger
class DatabaseService:
def __init__(self):
self.logger = Logger("MyApp", "database", destination="./logs")
def connect(self, host, port):
self.logger.start(f"Connecting to {host}:{port}")
try:
# Connection logic here...
self.logger.success("Connected successfully")
return True
except Exception as e:
self.logger.error(f"Connection failed: {e}")
return False
def query(self, sql):
self.logger.info(f"Executing query: {sql[:50]}...")
try:
# Query logic here...
self.logger.success("Query executed")
return {"rows": 42}
except Exception as e:
self.logger.error(f"Query failed: {e}")
raise
# Usage
db = DatabaseService()
db.connect("localhost", 5432)
db.query("SELECT * FROM users WHERE active = true")
Grafana Integration
GrafanaSink sends logs to Grafana in the background — batched, non-blocking, and zero-dependency (pure stdlib). It works with both Grafana Cloud (via OTLP) and self-hosted Loki.
Grafana Cloud (OTLP)
from steely import Logger
sink = Logger.set_global_grafana(
url="https://otlp-gateway-prod-sa-east-1.grafana.net",
labels={"service.name": "my-api", "deployment.environment": "production"},
auth=("YOUR_INSTANCE_ID", "YOUR_GRAFANA_API_KEY"),
)
log = Logger.getLogger("my-api")
log.info("Server started")
log.error("Unhandled exception")
# Logs are queued → batched → sent to Grafana Cloud in the background
Find your instance ID and API key in Grafana Cloud → My Account → Stack details.
Self-hosted Loki
from steely import Logger
sink = Logger.set_global_grafana(
url="http://loki:3100",
labels={"app": "my-api", "env": "staging"},
protocol="loki",
)
Automatic shutdown
The sink registers an atexit handler — no need to call flush() or close() manually. All pending logs are flushed when the process exits (scripts, uvicorn graceful shutdown, etc.).
# Manual control is available if needed:
sink.flush() # drain queue and send immediately
sink.close() # stop worker thread, then flush
Parameters
| Parameter | Default | Description |
|---|---|---|
url |
— | Base URL of the target endpoint |
labels |
{} |
Static metadata attached to every batch |
protocol |
"otlp" |
"otlp" for Grafana Cloud, "loki" for self-hosted |
auth |
None |
(instance_id, api_key) tuple for Basic Auth |
token |
None |
Bearer token (alternative to auth) |
batch_size |
50 |
Max log records per HTTP request |
flush_interval |
5.0 |
Max seconds between automatic flushes |
timeout |
3 |
HTTP request timeout in seconds |
max_queue_size |
10_000 |
Max buffered records when Grafana is unreachable |
debug |
False |
Print HTTP status/errors to stderr |
FastAPI example
from fastapi import FastAPI
from steely import Logger
app = FastAPI()
Logger.set_global_grafana(
url="https://otlp-gateway-prod-sa-east-1.grafana.net",
labels={"service.name": "my-api"},
auth=("1234567", "glc_eyJ..."),
)
log = Logger.getLogger("my-api")
@app.get("/users/{user_id}")
async def get_user(user_id: int):
log.info(f"Fetching user {user_id}")
return {"user_id": user_id}
No extra configuration needed — the atexit handler flushes on uvicorn shutdown.
Email Providers
steely.email sends email over SMTP or an HTTP API (Resend, or any REST API via a generic provider) behind one provider-agnostic interface. Switch providers with a one-line change — the message you build and the result you get back are identical.
Full integration guide (recommended for anyone — human or agent — wiring email into a project):
EMAIL_PROVIDERS.md.
Install
pip install steely # SMTP only (pure stdlib, no extra deps)
pip install "steely[http]" # + Resend / generic HTTP API providers (installs httpx)
SMTP (no extra install)
from steely.email import EmailClient, EmailMessage
client = EmailClient(
"smtp",
server="smtp.hostinger.com", port=587,
username="noreply@acme.com", password="…",
)
result = client.send(EmailMessage(
to=["dest@example.com"],
subject="Welcome",
body_html="<h1>Hi</h1>",
body_text="Hi", # optional plain-text fallback
))
print(result.success, result.message_id)
Resend (needs steely[http])
client = EmailClient("resend", api_key="re_xxx", from_email="noreply@acme.com")
result = client.send(EmailMessage(to=["dest@example.com"], subject="Hi", body_html="<p>Hi</p>"))
Generic HTTP API — Mailchimp / SendGrid / Mailgun / … (needs steely[http])
client = EmailClient(
"api",
endpoint_url="https://api.vendor.com/v1/send",
api_key="…",
from_email="noreply@acme.com",
# request_body=callable_or_dict # customise the payload for the vendor
)
The result
client.send(...) always returns an EmailResult and never raises on a rejected send:
result.success # bool
result.message # human-readable status/error (never contains secrets)
result.provider # "smtp" | "resend" | "api"
result.message_id # provider id when available
result.status_code # HTTP status for API providers; None for SMTP
result.as_tuple() # (success, message, message_id)
Parameters (common)
| Provider | Key parameters |
|---|---|
"smtp" |
server, port, username, password, use_tls=True, timeout=30, from_email |
"resend" |
api_key, from_email, timeout=30, max_attempts=3 |
"api" / "http" |
endpoint_url, api_key, from_email, request_body, auth_header, auth_scheme, max_attempts=3 |
Legacy steely.smtp.SendEmail
The older from steely.smtp import SendEmail API is preserved unchanged (it now delegates to SMTPProvider internally). New code should prefer EmailClient / EmailMessage. See EMAIL_PROVIDERS.md for details.
Streaming STT
steely.stt streams audio to Deepgram, AssemblyAI, Google Cloud / Chirp, Azure AI Speech, Amazon Transcribe, or self-hosted WhisperLive behind one small, async, provider-agnostic interface. You push raw audio frames and consume a uniform stream of transcript events — switching providers is a one-line change.
Full integration guide (auth per provider, language codes, sample rates, reconnection, adding a backend):
STT_PROVIDERS.md. Read it before wiring STT into a worker.
Install
pip install steely # core steely.stt — NO new deps (stdlib asyncio)
pip install "steely[stt-deepgram]" # + Deepgram SDK
pip install "steely[stt-assemblyai]" # + AssemblyAI SDK
pip install "steely[stt-google]" # + Google Cloud Speech SDK
pip install "steely[stt-azure]" # + Azure Speech SDK
pip install "steely[stt-aws]" # + Amazon Transcribe streaming SDK
pip install "steely[stt-whisperlive]" # + WhisperLive client (websockets)
pip install "steely[stt-all]" # + all backends
Each backend's SDK is imported lazily inside its provider's constructor, so import steely.stt never fails when an SDK is absent — only constructing that provider does, raising ProviderNotAvailableError (loud, at construction time, never a silent failure mid-stream).
On Python 3.13+,
audioop(used for resampling) was removed from the stdlib; add theaudioextra:pip install "steely[audio]".
The 30-second version
import asyncio
from steely.stt import STTClient, STTConfig
async def main():
# 1) Pick a provider by name (+ its config). Or pass a provider instance.
client = STTClient("deepgram", api_key="dg_xxx")
# 2) Describe the frames you WILL push (this is the INPUT format, not the backend's).
config = STTConfig(language="pt-BR", sample_rate=48000, channels=1)
# 3) Open a session, push raw frames, iterate canonical events.
session = await client.open_session(config)
async with session:
async for frame in livekit_audio(): # your frame source
await session.push_frame(frame.data.tobytes()) # RAW bytes — adapter resamples
await session.end_input()
async for event in session: # interim... final
print(event.type.value, event.text, event.start, event.end)
asyncio.run(main())
To use a different backend, change only step 1 — everything else stays identical:
client = STTClient("assemblyai", api_key="aai_xxx")
client = STTClient("google") # GOOGLE_APPLICATION_CREDENTIALS from env
client = STTClient("azure", subscription_key="…", region="…")
client = STTClient("aws", region="us-east-1")
client = STTClient("whisperlive", endpoint_url="ws://my-host:9090")
Core types
| Type | What it is |
|---|---|
STTClient |
Front door. STTClient(provider_name, **creds) or STTClient(provider_instance). |
STTConfig |
Session config describing the input you push: model, language (BCP-47), sample_rate, encoding, channels, interim_results. |
STTSession |
A live session: await push_frame(bytes), await end_input(), await aclose(). Also an async iterator of events and an async context manager. |
STTEvent |
The single canonical event: type (interim/final), text, start/end (int milliseconds), optional speaker, confidence, language; .is_final helper. |
EventType |
EventType.INTERIM | EventType.FINAL. |
ReconnectPolicy |
Reconnection strategy. Pass to open_session(..., reconnect=...). |
STTConfig
STTConfig(
model="default", # canonical model; adapter maps to e.g. Deepgram "nova-2"
language="pt-BR", # canonical BCP-47 tag; adapter maps to the provider's code
sample_rate=16000, # Hz of the frames YOU push
encoding="pcm_s16le", # encoding of the frames YOU push
channels=1, # channels YOU push; adapter downmixes to mono
interim_results=True, # request partials where the provider supports them
)
The sample_rate/encoding/channels fields describe the audio you push — the adapter resamples/transcodes to whatever the backend needs. Push the raw frame; never resample in your own code.
Providers at a glance
Provider (name / aliases) |
Authenticate with | Extra |
|---|---|---|
Deepgram (deepgram) |
api_key= or DEEPGRAM_API_KEY |
stt-deepgram |
AssemblyAI (assemblyai) |
api_key= or ASSEMBLYAI_API_KEY |
stt-assemblyai |
Google / Chirp (google, chirp) |
credentials_path= or GOOGLE_APPLICATION_CREDENTIALS |
stt-google |
Azure AI Speech (azure) |
subscription_key= + region= (or AZURE_SPEECH_KEY + AZURE_SPEECH_REGION) |
stt-azure |
Amazon Transcribe (aws, transcribe) |
AWS credential chain + region= or AWS_REGION |
stt-aws |
WhisperLive (whisperlive, whisper) |
none (self-hosted); endpoint_url= or WHISPERLIVE_URL (default ws://localhost:9090) |
stt-whisperlive |
Fake (fake) |
none — in-memory scripted events for tests | — |
Pick a model with STTConfig(model=...) (e.g. Deepgram "nova-2", Google "chirp_2"); "default" lets each adapter pick a sensible model.
Transparent reconnection
Network drops are handled for you. The session's background receive pump consults a ReconnectPolicy: on a retryable drop it backs off and re-opens the stream, so your async for only sees a brief pause.
from steely.stt import ReconnectPolicy
policy = ReconnectPolicy(max_retries=5, base_delay=0.5, backoff=2.0, max_delay=10)
session = await client.open_session(config, reconnect=policy)
Set max_retries=0 to disable it; exhausted retries (or a non-retryable error) raise STTConnectionError at the consumer. Every network/backend failure surfaces as that one error type — no backend-native exception ever reaches your code.
Testing without a network
Use the "fake" provider — an in-memory backend implementing the same contract, no SDK required:
from steely.stt import STTClient, STTConfig, STTEvent, EventType
from steely.stt.providers.fake import FakeProvider
script = [STTEvent(EventType.FINAL, "olá mundo", 0, 900, language="pt-BR")]
client = STTClient(FakeProvider(script=script))
session = await client.open_session(STTConfig())
events = [ev async for ev in session] # replays your script, records pushed frames
A runnable end-to-end example (provider selected from STT_PROVIDER, defaults to fake) lives in examples/stt_streaming.py.
pprint
The pprint function enhances the standard print with automatic caller location information, making debugging faster and more efficient. It shows the file path and line number in a format that's clickable in most IDEs and terminals.
Basic Usage
from steely.pprint import pprint
def calculate_total(items):
subtotal = sum(items)
pprint(f"Subtotal: {subtotal}")
tax = subtotal * 0.1
pprint(f"Tax: {tax}")
total = subtotal + tax
pprint(f"Total: {total}")
return total
calculate_total([10, 20, 30])
Output:
[PPRINT] File "/path/to/your/script.py", line 4
Subtotal: 60
[PPRINT] File "/path/to/your/script.py", line 7
Tax: 6.0
[PPRINT] File "/path/to/your/script.py", line 10
Total: 66.0
With Custom Colors
You can customize the color of the output using the color parameter:
from steely.pprint import pprint
from steely.design import UnicodeColors
# Success message in green
pprint("Operation completed!", color=UnicodeColors.success)
# Error message in red
pprint("Something went wrong!", color=UnicodeColors.fail)
# Info message in cyan
pprint("Processing data...", color=UnicodeColors.success_cyan)
# Warning message in yellow
pprint("Low memory warning", color=UnicodeColors.alert)
Clickable Links
The file path and line number are formatted to be clickable in most modern IDEs and terminals:
- VS Code: Ctrl+Click (Cmd+Click on Mac) to jump to the line
- PyCharm: Click the link to navigate to the source
- Terminal: Many terminals support clicking file:line patterns
Use Cases
Perfect for:
- Quick debugging without setting up a full logger
- Tracking execution flow through complex functions
- Comparing values at different points in code
- Temporary debug statements that are easy to locate and remove later
FastAPI Integration
Steely provides decorators for FastAPI that automatically record your API requests for testing, documentation, and debugging purposes.
Postman Recorder
The postman decorator automatically captures requests and responses, generating Postman Collection v2.1 format files that can be imported directly into Postman.
Basic Usage
from fastapi import FastAPI
from steely.fastapi import recorder
app = FastAPI()
@app.get("/users/{user_id}")
@recorder.postman()
async def get_user(user_id: int):
return {"user_id": user_id, "name": "John Doe", "email": "john@example.com"}
@app.post("/users")
@recorder.postman()
async def create_user(name: str, email: str):
return {"id": 123, "name": name, "email": email}
Collections are saved to ./.postman_collections/<function_name>.json by default.
Grouping Endpoints
Group multiple endpoints into a single collection:
@app.get("/users")
@recorder.postman(collection_name="user_api")
async def list_users():
return [{"id": 1, "name": "John"}, {"id": 2, "name": "Jane"}]
@app.get("/users/{user_id}")
@recorder.postman(collection_name="user_api")
async def get_user(user_id: int):
return {"id": user_id, "name": "John"}
@app.post("/users")
@recorder.postman(collection_name="user_api")
async def create_user(name: str):
return {"id": 123, "name": name}
All three endpoints will be saved in ./.postman_collections/user_api.json.
Custom Output Directory
@app.get("/api/data")
@recorder.postman(output_dir="./docs/postman")
async def get_data():
return {"data": "example"}
Curl Recorder
The curl decorator captures requests and generates executable curl commands, perfect for sharing API examples or creating test scripts.
Basic Usage
from fastapi import FastAPI
from steely.fastapi import recorder
app = FastAPI()
@app.get("/users/{user_id}")
@recorder.curl()
async def get_user(user_id: int, include_email: bool = False):
return {"user_id": user_id, "name": "John"}
@app.post("/users")
@recorder.curl()
async def create_user(name: str, email: str):
return {"id": 123, "name": name, "email": email}
Scripts are saved to ./.curl_scripts/<function_name>.sh and are automatically made executable.
Running Generated Scripts
# Execute the generated curl commands
bash ./.curl_scripts/get_user.sh
# Or make it executable and run directly
chmod +x ./.curl_scripts/get_user.sh
./.curl_scripts/get_user.sh
Grouping Commands
Group multiple endpoints into a single script:
@app.get("/users")
@recorder.curl(script_name="user_api")
async def list_users():
return [{"id": 1, "name": "John"}]
@app.post("/users")
@recorder.curl(script_name="user_api")
async def create_user(name: str):
return {"id": 123, "name": name}
All commands will be appended to ./.curl_scripts/user_api.sh.
Custom Output Directory
@app.get("/api/data")
@recorder.curl(output_dir="./scripts")
async def get_data():
return {"data": "example"}
Combining Recorders
You can use both decorators together to generate both Postman collections and curl scripts:
from fastapi import FastAPI
from steely.fastapi import recorder
app = FastAPI()
@app.get("/users/{user_id}")
@recorder.postman(collection_name="api_docs")
@recorder.curl(script_name="api_tests")
async def get_user(user_id: int):
return {"user_id": user_id, "name": "John"}
This will create:
./.postman_collections/api_docs.json- Postman collection for documentation./.curl_scripts/api_tests.sh- Executable curl commands for testing
Benefits
- Automatic Documentation: Generate Postman collections from real API traffic
- Testing: Create reproducible test scripts without manual work
- Team Collaboration: Share API examples with teammates easily
- CI/CD Integration: Use generated curl scripts in your automated tests
- Zero Configuration: Works out of the box with sensible defaults
Advanced Usage
Using Individual Decorators
You can import decorators individually if you prefer:
from steely import cronos, log, scan
@log
def my_function():
pass
@cronos
def timed_function():
pass
@scan
def tracked_function():
pass
Using Design Components
Steely's design module provides terminal styling utilities you can use in your own code:
from steely.design import UnicodeColors as C, Symbols as S, TypeColors
# Colored output
print(f"{C.green}Success!{C.reset}")
print(f"{C.bold}{C.red}Error!{C.reset}")
# Symbols
print(f"{S.CHECK} Task completed")
print(f"{S.ARROW_RIGHT} Next step")
print(f"{S.CROSS} Failed")
# Type-based colors
value = [1, 2, 3]
color = TypeColors.get_color(value)
print(f"{color}{value}{C.reset}")
Examples
Web API Debugging
from steely import Dan
import requests
@Dan.log
@Dan.cronos
def fetch_user(user_id):
response = requests.get(f"https://api.example.com/users/{user_id}")
return response.json()
user = fetch_user(42)
Algorithm Profiling
from steely import Dan
@Dan.cronos
def bubble_sort(arr):
n = len(arr)
for i in range(n):
for j in range(0, n-i-1):
if arr[j] > arr[j+1]:
arr[j], arr[j+1] = arr[j+1], arr[j]
return arr
@Dan.cronos
def quick_sort(arr):
if len(arr) <= 1:
return arr
pivot = arr[len(arr) // 2]
left = [x for x in arr if x < pivot]
middle = [x for x in arr if x == pivot]
right = [x for x in arr if x > pivot]
return quick_sort(left) + middle + quick_sort(right)
import random
data = [random.randint(0, 1000) for _ in range(1000)]
bubble_sort(data.copy()) # See timing
quick_sort(data.copy()) # Compare timing
Debugging Complex Logic
from steely import Dan
@Dan.scan
def calculate_discount(price, quantity, member_status):
subtotal = price * quantity
if member_status == "gold":
discount_rate = 0.20
elif member_status == "silver":
discount_rate = 0.10
else:
discount_rate = 0.0
discount = subtotal * discount_rate
final_price = subtotal - discount
return final_price
calculate_discount(99.99, 3, "gold")
# See exactly how each variable is computed
Framework Compatibility
All Steely decorators preserve the original function's signature, making them compatible with frameworks that rely on function introspection:
FastAPI
from fastapi import FastAPI
from steely import Dan
app = FastAPI()
@app.get("/users/{user_id}")
@Dan.log
@Dan.cronos
async def get_user(user_id: int, include_email: bool = False):
return {"user_id": user_id, "include_email": include_email}
Flask
from flask import Flask
from steely import Dan
app = Flask(__name__)
@app.route("/hello/<name>")
@Dan.log
def hello(name):
return f"Hello, {name}!"
License
MIT License
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distributions
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file steely-1.0.3.2-py3-none-any.whl.
File metadata
- Download URL: steely-1.0.3.2-py3-none-any.whl
- Upload date:
- Size: 99.9 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via:
twine/6.2.0 CPython/3.12.3
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
ada2a1ba219c8b57368688f5e11b9bf1896030c77d1b24394244cd31badead30
|
|
| MD5 |
441950781d21162e98cca3a7da20f8f2
|
|
| BLAKE2b-256 |
dfaba250be6f3900ce4e330f9edae474ab242eb4fc1755692744be8866cccef6
|