hypertabular
Delimited text — CSV, TSV, any single-byte ASCII separator — and workbooks — XLSX and ODS — read a batch at a time into typed columns, with a HyperCast verdict for every cell.
pip install hypertabular
from hypertabular import Column, DelimitedReader, Dialect, Fault, SheetOptions, Success, Workbook
# The header first; then a plan that reads the columns by name, wherever the file put them.
with DelimitedReader.open("orders.csv", Dialect.CSV) as reader:
header = reader.header # Header(('id', 'name', 'score'))
plan = [
Column.i32(header.ordinal("id")), # KeyError naming the column if it is missing
Column.text(header.ordinal("name")),
Column.f64(header.ordinal("score")),
]
reader.bind(plan)
for batch in reader:
ids, names, scores = batch.columns
# A column at a time, as the core wrote it…
total = sum(scores.values) # a memoryview of C doubles
for row, fault in scores.faults():
print(row, fault.reason.name, scores.raw(row))
# …or a cell at a time, as HyperCast's union.
for row in range(batch.rows):
match scores[row]:
case Success(value):
print(names.values[row], value)
case Fault(reason, offset, length):
print(reason.name, "on line", batch.line(row), "in", scores.raw(row))
# A workbook reads into the same batch, its sheet header first or with the plan up front.
book = Workbook.open("orders.xlsx")
print(book.sheets) # (SheetInfo(name='Orders', hidden=False),)
sheet = book.sheet("Orders", SheetOptions())
sheet.bind([Column.i32(sheet.header.ordinal("id")), Column.text(sheet.header.ordinal("name"))])
for batch in sheet:
...
A plan known up front goes straight to the constructor — DelimitedReader.open(path, dialect, plan), book.sheet(which, options, plan) — which binds it before the header is read.
Header first
A reader made without a plan — DelimitedReader(source, dialect), DelimitedReader.open(path, dialect), book.sheet(which, options) — reads the header and waits: bind(plan) declares the
plan once, before the first read. A read before it raises RuntimeError (and a later bind
puts that right); so does a second bind. is_bound says which it is, and a delimited
reader's column_count is the header's width, or the first record's once it has been read.
The header is a Header: the tuple of str it always was, plus ordinal(name) — the first
column with exactly that name, case and spaces included, or a KeyError naming it — and
get(name, default=None), which returns default instead. A bytes name is matched against
the bytes the file holds.
Rows
A batch is column-major; a Row reads it across, for code that builds an object a row at a
time. for row in batch (or batch.iter_rows(), batch.row(i)) gives views — the batch and
an index, nothing copied — with index, line, get(column) (the cell as Success or
Fault), text(column) (a text cell's str, or None) and raw(column). reader.rows()
and sheet.rows() run across batches, reading the next as one runs out. A batch owns what it
shows, so a row stays valid after the reader has moved on.
with DelimitedReader.open("orders.csv", Dialect.CSV, plan) as reader:
orders = [
Order(id.value, row.text(1))
for row in reader.rows()
if isinstance(id := row.get(0), Success)
]
Streams and asyncio
DelimitedReader(source, …) takes bytes or a binary file object (anything with
read(size)), and so does Workbook(data): a workbook is read to the end into memory it owns,
since a zip is read from its directory at the end back. Either way the format is read from the
bytes. A file object is the caller's to close.
An asynchronous stream — an asyncio.StreamReader, or anything with async read(size) — is
read with asyncio:
reader = await DelimitedReader.open_async(stream, Dialect.CSV) # the header is awaited too
reader.bind([Column.i64(reader.header.ordinal("id"))])
async for batch in reader: # or: await reader.read_async()
...
book = await Workbook.open_async(stream)
The core never waits: when a read needs input it says how much, the stream is awaited for that
much and the read goes on, all the core's work done between awaits with the interpreter
released. Cancellation is asyncio's, and a read cancelled while it awaits the stream leaves the
reader where it was — the next read carries on. read_async and async for work on any
reader; over bytes or a blocking file object they complete without awaiting anything.
The shape
The native core owns no memory and reads no files. It is linked straight into a CPython
extension module (hypertabular._native, PyO3), and the extension is the binding: it
allocates a value array and a verdict array per column, once, and the core fills them in one
call per batch with the interpreter released. A column reaches Python whole — a read-only
memoryview of the door's own item type, which anything that takes a buffer takes — with no
Python call per cell.
- One batch type. Iterating a reader or a sheet (or calling
read()) gives aBatch:rows,columns,column(i),line(row),raw(column, row),get(column, row)andtext(column, row), and its rows when iterated. Each column is aColumnDatawithvalues,verdicts,fault_count,faults(),raw(row)andcolumn[row]for one cell asSuccessorFault. A batch owns what it shows: it stays valid after the reader has moved on. - Nothing is sniffed. The
Dialectstates the separator, the quoting and the header;SheetOptionsstates a sheet's header, whether empty rows are skipped and the batch size; the plan states each column's door and, for numbers, itsNumFormat. - HyperCast is the judge.
Success,Fault,CastFailure,NumFormat,UnixPrecision,DateOrderandExcelEpochare thehypercastpackage's own objects, re-exported here unchanged. A text cell means exactly whathypercast.cast_*says of the same text, a typed workbook cell is converted by the door directly, and its value is the Python type that door gives:int,float,bool,decimal.Decimal,uuid.UUID,datetime,date,time,timedelta, andstrfor text. - A bad value is a verdict; a broken file is an exception. A cell that does not cast is
a
Faultin its column and the read goes on. A record of the wrong width, input that ends inside a quoted cell, a workbook whose container or parts cannot be read, raisesTabularError— after every intact row before it has been delivered.
hypertabular.native_version() reports the core the extension was built from.
Platforms
One abi3 wheel per platform serves every CPython from 3.11 up, so nothing is compiled on
install: Linux (glibc and musl) on x86-64 and arm64, macOS on Apple silicon and Intel, and
Windows on x86-64 and arm64. The free-threaded build (python3.14t) is not one of them: an
abi3 wheel serves only the GIL build, and there is no source distribution to compile.
In the browser (Pyodide)
The same PyO3 extension, compiled for Pyodide's Emscripten target, is published to PyPI as a
ninth wheel, hypertabular-X.Y.Z-cp311-abi3-pyemscripten_2026_0_wasm32.whl, so micropip
finds it the way pip finds the native wheels, and HyperCast's beside it:
import micropip
await micropip.install("hypertabular")
import hypertabular
hypertabular.BACKEND # "native"
hypertabular.native_version() # the linked core's version
It is the same native extension, with the same API and no JavaScript bridge. CI installs the
wheel into Pyodide and runs this package's whole pytest suite in it twice, under Node and in
headless Chrome, corpus replay included; the one test that starts threads is skipped, since
Pyodide cannot. The wheel is for Pyodide 314.x (Python 3.14, platform
pyemscripten_2026_0): each Pyodide ABI year needs its own wheel.
Verifying provenance
Every wheel is built and attested by the SkunkWerkx forge's reusable workflow:
gh attestation verify hypertabular-<version>-*.whl --repo SkunkWerkx/HyperTabular --signer-repo SkunkWerkx/.github
License
Metadata
Release files for hypertabular 0.8.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Reset | |||
|---|---|---|---|---|
| hypertabular-0.8.0-cp311-abi3-win_arm64.whl | CPython 3.11 | abi3 | Windows ARM64 | Details |
| hypertabular-0.8.0-cp311-abi3-win_amd64.whl | CPython 3.11 | abi3 | Windows x86-64 | Details |
| hypertabular-0.8.0-cp311-abi3-pyemscripten_2026_0_wasm32.whl | CPython 3.11 | abi3 | PyEmscripten 2026.0+ WebAssembly | Details |
| hypertabular-0.8.0-cp311-abi3-musllinux_1_2_x86_64.whl | CPython 3.11 | abi3 | Linux musl 1.2+ x86-64 | Details |
| hypertabular-0.8.0-cp311-abi3-musllinux_1_2_aarch64.whl | CPython 3.11 | abi3 | Linux musl 1.2+ ARM64 | Details |
| hypertabular-0.8.0-cp311-abi3-manylinux_2_28_x86_64.whl | CPython 3.11 | abi3 | Linux glibc 2.28+ x86-64 | Details |
| hypertabular-0.8.0-cp311-abi3-manylinux_2_28_aarch64.whl | CPython 3.11 | abi3 | Linux glibc 2.28+ ARM64 | Details |
| hypertabular-0.8.0-cp311-abi3-macosx_11_0_arm64.whl | CPython 3.11 | abi3 | macOS 11.0+ ARM64 | Details |
| hypertabular-0.8.0-cp311-abi3-macosx_10_12_x86_64.whl | CPython 3.11 | abi3 | macOS 10.12+ x86-64 | Details |
Total release size: 4.1 MB
Release files / hypertabular-0.8.0-cp311-abi3-win_arm64.whl
| Download URL | hypertabular-0.8.0-cp311-abi3-win_arm64.whl |
|---|---|
| Size | 367.9 kB |
| Tags | CPython 3.11 Windows ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
72a0d08f691dcce41cfd13c250177355dfba767b6c8a7aca0fb49d3b7f562544
|
|
BLAKE2b-256 checksum How to use checksums |
62f141425871a9193784975b7fc7390667eecb52b151d8cb38a5d3817a8eb321
|
| 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 9, 2026.
Transparency logRelease files / hypertabular-0.8.0-cp311-abi3-win_amd64.whl
| Download URL | hypertabular-0.8.0-cp311-abi3-win_amd64.whl |
|---|---|
| Size | 391.1 kB |
| Tags | CPython 3.11 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
ead56c72b68233c5e736e7579a148debc8dea3da52c8dd2fcd57918bd65800ea
|
|
BLAKE2b-256 checksum How to use checksums |
7bea53c9b39feb9d93afd778741c0030724360e6c065128136f74d8a6c9497af
|
| 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 9, 2026.
Transparency logRelease files / hypertabular-0.8.0-cp311-abi3-pyemscripten_2026_0_wasm32.whl
| Download URL | hypertabular-0.8.0-cp311-abi3-pyemscripten_2026_0_wasm32.whl |
|---|---|
| Size | 223.3 kB |
| Tags | CPython 3.11 PyEmscripten 2026.0+ WebAssembly abi3 |
|
SHA-256 checksum How to use checksums |
435abc86a78c906004ce0734183b051b1557c2ec7d96929d725f98a47ca1082c
|
|
BLAKE2b-256 checksum How to use checksums |
db553382c2f8e91f43c918d9158865b9d785f2329b2ca9100fc966692805e6f7
|
| 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 9, 2026.
Transparency logRelease files / hypertabular-0.8.0-cp311-abi3-musllinux_1_2_x86_64.whl
| Download URL | hypertabular-0.8.0-cp311-abi3-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 676.8 kB |
| Tags | CPython 3.11 Linux musl 1.2+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
70e564689654711f312446c02ad182989ba493ef410228067cada961677ef9d2
|
|
BLAKE2b-256 checksum How to use checksums |
9ab954ed1191a786d780d5d83f20911c1282955657ca91b05e510b7d662264ce
|
| 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 9, 2026.
Transparency logRelease files / hypertabular-0.8.0-cp311-abi3-musllinux_1_2_aarch64.whl
| Download URL | hypertabular-0.8.0-cp311-abi3-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 615.2 kB |
| Tags | CPython 3.11 Linux musl 1.2+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
ed422271e62e994c6d0fe1e3560a1ce54f1ade4e9723555efdf2759c3141f8e7
|
|
BLAKE2b-256 checksum How to use checksums |
094cbdac5b014b2c9dc650951b3c322c846c466d413e777d5fe3cf83787febca
|
| 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 9, 2026.
Transparency logRelease files / hypertabular-0.8.0-cp311-abi3-manylinux_2_28_x86_64.whl
| Download URL | hypertabular-0.8.0-cp311-abi3-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 464.6 kB |
| Tags | CPython 3.11 Linux glibc 2.28+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
971992aeadc2cdc4997cd4439f27151abe2ef1a3eecfa337a081375987577eb2
|
|
BLAKE2b-256 checksum How to use checksums |
5e10c4c8f7b7915078d63f050e3634c2eaebc9968142b2a3a05208199b380fbe
|
| 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 9, 2026.
Transparency logRelease files / hypertabular-0.8.0-cp311-abi3-manylinux_2_28_aarch64.whl
| Download URL | hypertabular-0.8.0-cp311-abi3-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 437.4 kB |
| Tags | CPython 3.11 Linux glibc 2.28+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
6719ed32dc3912fc8b91c64bed67afc44956cab80ced312fb0add8059412d55d
|
|
BLAKE2b-256 checksum How to use checksums |
5575ca4d3424ebae2b5268489544d71a6e4946fe7a77e25466bc66ff799cb317
|
| 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 9, 2026.
Transparency logRelease files / hypertabular-0.8.0-cp311-abi3-macosx_11_0_arm64.whl
| Download URL | hypertabular-0.8.0-cp311-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 427.1 kB |
| Tags | CPython 3.11 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
fce283af27e95c5b972e087bf610b1459690e8133f466129b540ecf17ebf5ad3
|
|
BLAKE2b-256 checksum How to use checksums |
ff1aca2ca2890e98a721c4fd007421cc8a08b749c55e22c6262ddd5df1d7a8d1
|
| 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 9, 2026.
Transparency logRelease files / hypertabular-0.8.0-cp311-abi3-macosx_10_12_x86_64.whl
| Download URL | hypertabular-0.8.0-cp311-abi3-macosx_10_12_x86_64.whl |
|---|---|
| Size | 456.0 kB |
| Tags | CPython 3.11 abi3 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
e7dc34ab4c42683239f7d1f73c0121de8dbe71f7efa84fe262c030c8a7aecacb
|
|
BLAKE2b-256 checksum How to use checksums |
110f43c87bc12c733571c54e1179931736d7f70188d3e89d5d04abc0fab54970
|
| 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 9, 2026.
Transparency log