liquidcarbon

no, but it's one step away with gzip.decompress or similar; if we know the exact position, we can retrieve it with range reads, roughly like this:

aws s3api get-object --bucket mybucket --key partially_human_friendly_blob --range bytes=start-end | cut or awk | gunzip

DuckDB is amazing, I'm using it every day.

It would be marginally useful here though. I really just want to get the binary compressed blob. Fun fact: MS SQL Server has "DECOMPRESS" and DuckDB does not.

It's actually not hard to implement if you separate the index file from the blobs... but the append part probably won't be feasible with S3

- fast cross-platform CLI (Bash, Windows) that transparently wraps Pixi and uv, for best of both worlds

- base layer python is completely isolated from OS or other python environments - everything lives in one folder, nothing goes on PATH

- generates notebook kernels

- generates, executes notebooks from CLI

- from zero python to deployed app in a few commands that can be packaged into a single Bash or Powershell script (examples in .github/workflows)