Python bindings for ggsql, a SQL extension for declarative data visualization.
This package provides Python bindings to the Rust ggsql crate, enabling Python users to create visualizations using ggsql's VISUALISE syntax with native Altair chart output.
Installation
From PyPI (when published)
pip install ggsql
From source
Building from source requires:
# Clone the repository git clone https://github.com/posit-dev/ggsql-python.git cd ggsql-python # Create a virtual environment python -m venv .venv source .venv/bin/activate # or `.venv\Scripts\activate` on Windows # Install build dependencies pip install maturin # Build and install in development mode maturin develop # Or build a wheel maturin build --release pip install target/wheels/ggsql-*.whl
Quick Start
Simple Usage with render_altair
For quick visualizations, use the render_altair convenience function. It accepts any narwhals-compatible DataFrame (polars, pandas, pyarrow, etc.):
import ggsql import pyarrow as pa # Create a table table = pa.table({ "x": [1, 2, 3, 4, 5], "y": [10, 20, 15, 30, 25], "category": ["A", "B", "A", "B", "A"] }) # Render to Altair chart chart = ggsql.render_altair(table, "VISUALISE x, y DRAW point") # Display or save chart.display() # In Jupyter chart.save("chart.html") # Save to file
Two-Stage API
For more control, use the two-stage API with explicit reader and writer:
import ggsql import pyarrow as pa # 1. Create a DuckDB reader reader = ggsql.DuckDBReader("duckdb://memory") # 2. Register your data as a table (accepts pyarrow, polars, pandas, etc.) table = pa.table({ "date": ["2024-01-01", "2024-01-02", "2024-01-03"], "revenue": [100, 150, 120], "region": ["North", "South", "North"] }) reader.register("sales", table) # 3. Execute the ggsql query spec = reader.execute( """ SELECT * FROM sales VISUALISE date AS x, revenue AS y, region AS color DRAW line LABEL title => 'Sales by Region' """ ) # 4. Inspect metadata print(f"Rows: {spec.metadata()['rows']}") print(f"Columns: {spec.metadata()['columns']}") print(f"Layers: {spec.layer_count()}") # 5. Inspect SQL/VISUALISE portions and data print(f"SQL: {spec.sql()}") print(f"Visual: {spec.visual()}") print(spec.layer_data(0)) # Returns pyarrow.Table # 6. Render to Vega-Lite JSON writer = ggsql.VegaLiteWriter() vegalite_json = writer.render(spec) print(vegalite_json)
API Reference
Classes
DuckDBReader(connection: str)
Database reader that executes SQL and manages DataFrames.
reader = ggsql.DuckDBReader("duckdb://memory") # In-memory database reader = ggsql.DuckDBReader("duckdb:///path/to/file.db") # File database
Methods:
register(name: str, table, replace: bool = False)- Register data as a queryable table (acceptspyarrow.Table,polars.DataFrame,pandas.DataFrame, etc.)unregister(name: str)- Unregister a previously registered tableexecute_sql(sql: str) -> pyarrow.Table- Execute SQL and return results
VegaLiteWriter()
Writer that generates Vega-Lite v6 JSON specifications.
writer = ggsql.VegaLiteWriter() json_output = writer.render(spec)
Validated
Result of validate() containing query analysis without SQL execution.
Methods:
valid() -> bool- Whether the query is syntactically and semantically validhas_visual() -> bool- Whether the query contains a VISUALISE clausesql() -> str- The SQL portion (before VISUALISE)visual() -> str- The VISUALISE portionerrors() -> list[dict]- Validation errors with messages and locationswarnings() -> list[dict]- Validation warnings
Spec
Result of reader.execute(), containing resolved visualization ready for rendering.
Methods:
metadata() -> dict- Get{"rows": int, "columns": list[str], "layer_count": int}sql() -> str- The executed SQL queryvisual() -> str- The VISUALISE clauselayer_count() -> int- Number of DRAW layersdata() -> pyarrow.Table | None- Main query result datalayer_data(index: int) -> pyarrow.Table | None- Layer-specific data (if filtered)stat_data(index: int) -> pyarrow.Table | None- Statistical transform datalayer_sql(index: int) -> str | None- Layer filter SQLstat_sql(index: int) -> str | None- Stat transform SQLwarnings() -> list[dict]- Validation warnings from execution
Functions
validate(query: str) -> Validated
Validate query syntax and semantics without executing SQL.
validated = ggsql.validate("SELECT x, y FROM data VISUALISE x, y DRAW point") if validated.valid(): print("Query is valid!") else: for error in validated.errors(): print(f"Error: {error['message']}")
reader.execute(query: str) -> Spec
Execute a ggsql query and return the visualization specification.
reader = ggsql.DuckDBReader("duckdb://memory") spec = reader.execute("SELECT 1 AS x, 2 AS y VISUALISE x, y DRAW point")
render_altair(df, viz: str, **kwargs) -> altair.Chart
Convenience function to render a DataFrame with a VISUALISE spec to an Altair chart.
Parameters:
df- Any narwhals-compatible DataFrame (polars, pandas, etc.). LazyFrames are collected automatically.viz- The VISUALISE specification string**kwargs- Additional arguments passed toaltair.Chart.from_json()(e.g.,validate=False)
Returns: An Altair chart object (Chart, LayerChart, FacetChart, etc.)
import pyarrow as pa import ggsql table = pa.table({"x": [1, 2, 3], "y": [10, 20, 30]}) chart = ggsql.render_altair(table, "VISUALISE x, y DRAW point")
Examples
Mapping Styles
import pyarrow as pa table = pa.table({"x": [1, 2, 3], "y": [10, 20, 30], "category": ["A", "B", "A"]}) # Explicit mapping ggsql.render_altair(table, "VISUALISE x AS x, y AS y DRAW point") # Implicit mapping (column name = aesthetic name) ggsql.render_altair(table, "VISUALISE x, y DRAW point") # Wildcard mapping (map all matching columns) ggsql.render_altair(table, "VISUALISE * DRAW point") # With color encoding ggsql.render_altair(table, "VISUALISE x, y, category AS color DRAW point")
Custom Readers
You can use any Python object with an execute_sql(sql: str) method as a reader. The method should return a pyarrow.Table (or any type that pyarrow.table() can convert, such as a polars.DataFrame).
import ggsql import pyarrow as pa import pyarrow.csv class CSVReader: """Custom reader that loads data from CSV files.""" def __init__(self, data_dir: str): self.data_dir = data_dir def execute_sql(self, sql: str) -> pa.Table: # Simple implementation: ignore SQL and return fixed data # A real implementation would parse SQL to determine which file to load return pyarrow.csv.read_csv(f"{self.data_dir}/data.csv") # Use custom reader with ggsql.execute() reader = CSVReader("/path/to/data") spec = ggsql.execute( "SELECT * FROM data VISUALISE x, y DRAW point", reader ) writer = ggsql.VegaLiteWriter() json_output = writer.render(spec)
Additional methods for custom readers:
register(name: str, table, replace: bool = False) -> None- Register data as a queryable table (required). Receives apyarrow.Table.unregister(name: str) -> None- Unregister a previously registered table (optional)
class AdvancedReader: """Custom reader with registration support.""" def __init__(self): self.tables = {} def execute_sql(self, sql: str) -> pa.Table: # Your SQL execution logic here ... def register(self, name: str, table: pa.Table, replace: bool = False) -> None: self.tables[name] = table def unregister(self, name: str) -> None: del self.tables[name]
Native readers like DuckDBReader use an optimized fast path, while custom Python readers are automatically bridged via IPC serialization.
Ibis Reader Example
Ibis provides a unified Python API for SQL operations across multiple backends. Here's how to create an ibis-based custom reader:
import ggsql import pyarrow as pa import ibis class IbisReader: """Custom reader using ibis as the SQL backend.""" def __init__(self, backend="duckdb"): if backend == "duckdb": self.con = ibis.duckdb.connect() elif backend == "sqlite": self.con = ibis.sqlite.connect() # Add other backends as needed def execute_sql(self, sql: str) -> pa.Table: return self.con.con.execute(sql).arrow() def register(self, name: str, table: pa.Table, replace: bool = False) -> None: self.con.create_table(name, table, overwrite=replace) def unregister(self, name: str) -> None: self.con.drop_table(name) # Usage reader = IbisReader() table = pa.table({ "date": ["2024-01-01", "2024-01-02", "2024-01-03"], "revenue": [100, 150, 120], }) reader.register("sales", table) spec = ggsql.execute( "SELECT * FROM sales VISUALISE date AS x, revenue AS y DRAW line", reader ) writer = ggsql.VegaLiteWriter() print(writer.render(spec))
Development
Building
# Rebuild after Rust changes
maturin developTo pick up a new version of the upstream ggsql Rust crate, bump its version in Cargo.toml and re-run maturin develop.
Running tests
# Install test dependencies pip install pytest # Run all tests pytest tests/ -v
Requirements
- Python >= 3.10
- altair >= 5.0
- narwhals >= 2.15
- pyarrow >= 14.0
License
MIT