xbbg
Python / PyPI package for notebooks, research workflows, scheduled pipelines, and Python services that work with licensed Bloomberg data.
Package map
Two public packages. One shared engine.
Choose Python or Node.js at the application edge. The request model, Bloomberg C++ SDK integration, async workers, middleware hooks, and Arrow-native outputs stay aligned underneath.
Public surfaces
@xbbg/core
Node.js / npm package for services that need the same typed request model and async engine outside Python.
Rust / Arrow core
Shared implementation for sessions, worker pools, typed requests, Bloomberg C++ SDK integration, request middleware, and Arrow outputs.
| Package | Ecosystem | Registry | Install | Best fit |
|---|---|---|---|---|
xbbg | Python / PyPI | PyPI | pip install xbbg | Python notebooks, research jobs, data pipelines, and services |
@xbbg/core | Node.js / npm | npm | npm install @xbbg/core | Node.js services that need matching Bloomberg-data behavior |
What stays shared
- 01Typed requests
Dates, fields, overrides, auth, retries, and output shape use the same model across runtimes.
- 02Async runtime
Reusable sessions and worker pools live in the Rust engine instead of separate Python and Node integrations.
- 03Middleware
Request middleware gives production teams one place for tracing, metrics, audit tags, policy checks, and compliance hooks.
- 04Outputs
Arrow-native results feed pandas, Polars, PyArrow, DuckDB, Narwhals, and JavaScript objects.
Implementation details
The platform-specific npm packages used by @xbbg/core, Rust crates, binding crates, and private monorepo packages are implementation details. Public docs stay centered on the installable packages users choose directly.
Next steps
- Python docs — use the shared engine from Python
- JavaScript docs — use the shared engine from Node.js
- Architecture / Shared Engine — see the request path
- Release notes — track behavior and API changes