pybufarrow
Turn raw protobuf bytes into Apache Arrow RecordBatches — without deserializing, without codegen, without copying data.
pybufarrow wraps bufarrowlib, a Go library that transcodes serialized protobuf messages directly into Arrow columnar format using zero-copy memory sharing via the Arrow C Data Interface. Give it a .proto file and a stream of raw bytes; get back a pyarrow.RecordBatch you can hand straight to Pandas, Polars, DuckDB, or write to Parquet.
It's fast: the underlying engine processes ~300K messages/sec on production-shaped data — 39% faster than hand-written Arrow builders — while using 57% fewer allocations per message.
When to use pybufarrow
- Kafka / Pub-Sub consumers that receive protobuf-encoded messages and need them in columnar format for analytics, dashboards, or data lake ingestion.
- ETL pipelines where protobuf is the wire format from upstream services and the destination is Parquet, Delta Lake, or a columnar database.
- Streaming into DuckDB — denormalize protobuf messages into flat Arrow RecordBatches and append them directly to DuckDB. Aggregating pre-flattened data is orders of magnitude faster than querying nested structures.
- Ad-tech / real-time bidding — denormalize nested messages like OpenRTB BidRequests into flat, query-friendly tables with a single YAML config.
- Data science notebooks — skip the
proto → dict → DataFramedance. Go straight from wire bytes to Arrow-backed DataFrames with type fidelity. - Feature stores / ML pipelines that ingest protobuf event streams and need low-latency materialization into Parquet or Arrow IPC.
Installation
pip install pybufarrow
Or from source (using uv):
# Build the shared library
cd bufarrowlib/cbinding && make build
# Copy into the Python package
cp cbinding/libbufarrow.so python/pybufarrow/
# Install
cd python && uv sync
Quick Start
from pybufarrow import HyperType, Transcoder
# HyperType compiles a high-performance parser from your .proto definition.
# Share one instance across all transcoders — it's thread-safe.
ht = HyperType("events.proto", "UserEvent")
with Transcoder.from_proto_file("events.proto", "UserEvent", hyper_type=ht) as tc:
# Feed raw protobuf bytes — no deserialization needed
for raw_bytes in kafka_consumer:
tc.append(raw_bytes)
# Flush to a zero-copy pyarrow RecordBatch
batch = tc.flush()
# Use it anywhere Arrow is accepted
df = batch.to_pandas()
import duckdb
duckdb.sql("SELECT * FROM batch WHERE event_type = 'purchase'")
Streaming Batches
Process millions of messages without holding everything in memory. transcode_batch yields fixed-size RecordBatches as an iterator:
from pybufarrow import transcode_batch
# Yield 122880-row batches from a message stream
for batch in transcode_batch("events.proto", "UserEvent", message_stream, batch_size=122880):
# Write each batch to a Parquet dataset, push to a queue, etc.
writer.write_batch(batch)
Collect everything into a single Arrow Table, or write directly to Parquet:
from pybufarrow import transcode_to_table, transcode_to_parquet
# Arrow Table — ready for Polars, DuckDB, or any Arrow-native tool
table = transcode_to_table("events.proto", "UserEvent", messages)
# Straight to Parquet — no intermediate DataFrame
transcode_to_parquet("events.proto", "UserEvent", messages, "events.parquet")
Denormalization
Protobuf messages are often deeply nested — repeated fields, nested sub-messages, maps. Querying nested Arrow structs is painful. pybufarrow can flatten (denormalize) nested messages into wide, query-friendly rows with fan-out on repeated fields.
With a YAML config
# denorm.yaml
proto_file: order.proto
message_name: Order
denorm:
columns:
- name # top-level scalar
- items[*].id # fan-out: one row per item
- items[*].price
- seq
with Transcoder.from_config("denorm.yaml") as tc:
for raw in order_stream:
tc.append_denorm(raw)
flat = tc.flush_denorm()
# An order with 3 items produces 3 rows, each with the parent's `name` and `seq`
Programmatic column selection
ht = HyperType("order.proto", "Order")
with Transcoder.from_proto_file(
"order.proto", "Order",
hyper_type=ht,
denorm_columns=["name", "items[*].id", "items[*].price", "seq"],
) as tc:
tc.append_denorm(raw_order)
flat = tc.flush_denorm()
print(flat.to_pandas())
# name id price seq
# acme sku-1 9.99 1
# acme sku-2 4.50 1
Empty repeated fields produce one row with nulls (left-join semantics), so you never lose parent records.
Why denormalize?
Nested protobuf structures are great for wire transport but terrible for analytics. Querying nested Arrow structs or repeated fields requires unnesting at query time — which is expensive and makes aggregations slow. The denormalizer does the fan-out once at ingest time, producing flat columns that DuckDB, Pandas, and Polars can aggregate at full speed:
import duckdb
con = duckdb.connect("pipeline.duckdb")
# Create table from the first denormalized batch (schema inferred from Arrow)
con.execute("CREATE TABLE IF NOT EXISTS events AS SELECT * FROM flat_batch LIMIT 0")
# Append denormalized RecordBatches — zero-copy via Arrow
con.execute("INSERT INTO events SELECT * FROM flat_batch")
# Standard SQL on simple, flat columns — orders of magnitude faster than nested
con.sql("""
SELECT service_name, count(*) as events, avg(latency_ms)
FROM events
GROUP BY service_name
ORDER BY event_tm DESC
""")
Merging Multiple Protobuf Messages
When your pipeline enriches a base message with sidecar data (e.g., a bid request plus server-side metadata), append both in a single call:
with Transcoder.from_proto_file(
"bidrequests.proto", "BidRequest",
custom_proto="server_meta.proto",
custom_message="ServerMeta",
) as tc:
tc.append_merged(bid_request_bytes, server_meta_bytes)
batch = tc.flush()
# The resulting schema includes columns from both messages
Parallel Processing with Clone
clone() creates an independent transcoder that shares the same compiled schema and HyperType. Use it to fan out across threads:
import concurrent.futures
from pybufarrow import HyperType, Transcoder
ht = HyperType("events.proto", "UserEvent")
base_tc = Transcoder.from_proto_file("events.proto", "UserEvent", hyper_type=ht)
def process_partition(partition):
with base_tc.clone() as tc:
for msg in partition:
tc.append(msg)
return tc.flush()
with concurrent.futures.ThreadPoolExecutor(max_workers=4) as pool:
batches = list(pool.map(process_partition, partitioned_messages))
Parquet I/O
Write Arrow data to Parquet and read it back — useful for materializing transcoded streams to disk:
with Transcoder.from_proto_file("events.proto", "UserEvent", hyper_type=ht) as tc:
for msg in messages:
tc.append(msg)
# Write directly to Parquet (no intermediate pyarrow step)
tc.write_parquet("events.parquet")
# Read back as a RecordBatch, optionally selecting columns by index
batch = tc.read_parquet("events.parquet", columns=[0, 1, 3])
Architecture
Python user code
↓ Pythonic API
pybufarrow (ctypes)
↓ C ABI via Arrow C Data Interface
libbufarrow.so (CGo shared library)
↓ hyperpb TDP parser (2–3× faster than generated code)
bufarrowlib (Go)
↓ zero-copy Arrow record batches
pyarrow
No gRPC. No protoc codegen. No serialization round-trips. The Arrow C Data Interface means RecordBatches cross the Go→Python boundary without copying memory.
API Reference
Core Classes
| Class | Purpose |
|---|---|
Transcoder |
Ingests raw protobuf bytes, flushes Arrow RecordBatches |
HyperType |
Compiles a high-performance parser from a .proto file. Thread-safe, shareable across transcoders |
BufarrowError |
Raised on invalid protos, missing configs, use-after-close, etc. |
Transcoder Constructors
| Constructor | Use when |
|---|---|
Transcoder.from_proto_file(proto, msg, ...) |
You have a .proto file |
Transcoder.from_config(path) |
You have a YAML config with denorm rules |
Transcoder.from_config_string(yaml) |
Same, but the YAML is a string |
Transcoder Methods
| Method | Description |
|---|---|
append(data) |
Ingest raw protobuf bytes (requires HyperType) |
append_merged(base, custom) |
Ingest two protobuf messages as one row (requires custom_proto) |
append_denorm(data) |
Ingest with denormalization / fan-out (requires HyperType + denorm plan) |
flush() → RecordBatch |
Flush accumulated rows as a zero-copy Arrow RecordBatch |
flush_denorm() → RecordBatch |
Flush denormalized rows |
write_parquet(path) |
Write buffered data to Parquet |
read_parquet(path, columns=None) |
Read Parquet file back as a RecordBatch |
clone() → Transcoder |
Create an independent copy for parallel use |
schema |
Arrow schema (cached) |
field_names |
List of field name strings |
Batch Helpers
| Function | Description |
|---|---|
transcode_batch(proto, msg, messages, batch_size=1024) |
Iterator of fixed-size RecordBatches |
transcode_merged_batch(proto, msg, messages, batch_size=1024) |
Same, for merged (base, custom) message pairs |
transcode_to_table(proto, msg, messages) |
Collect all messages into a single pyarrow.Table |
transcode_to_parquet(proto, msg, messages, path) |
Transcode and write directly to Parquet |
Requirements
- Python >= 3.9
- pyarrow >= 14.0
libbufarrow.so/libbufarrow.dylibshared library (built from Go source viamake buildincbinding/)
License
Apache-2.0
Release files for pybufarrow 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
Total release size: 271.6 MB
Release files / pybufarrow-0.1.0-cp313-cp313-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | pybufarrow-0.1.0-cp313-cp313-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 20.4 MB |
| Tags | CPython 3.13 Linux glibc 2.17+ ARM64 |
|
SHA-256 checksum How to use checksums |
07a4e2d1a29913cc2b312678a82c6845a7b02dcc1b74db5df27c383fb3231a6b
|
|
BLAKE2b-256 checksum How to use checksums |
4bb225d446d3f44ab759e83a17d137210132e6894c6aad9a5c38826406f25abf
|
| 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 Aug 13, 2026.
Transparency logRelease files / pybufarrow-0.1.0-cp313-cp313-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | pybufarrow-0.1.0-cp313-cp313-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 23.0 MB |
| Tags | CPython 3.13 Linux glibc 2.17+ x86-64 Linux glibc 2.5+ x86-64 |
|
SHA-256 checksum How to use checksums |
6c76337010b2262e00aa783d0d281d3ce723829d9a4ba2485f014162c15841d5
|
|
BLAKE2b-256 checksum How to use checksums |
8f584b9c145e1960d69b328548aa84b372f9cb9836b6363fe0fdc4eb290e9f7b
|
| 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 Aug 13, 2026.
Transparency logRelease files / pybufarrow-0.1.0-cp313-cp313-macosx_11_0_arm64.whl
| Download URL | pybufarrow-0.1.0-cp313-cp313-macosx_11_0_arm64.whl |
|---|---|
| Size | 11.0 MB |
| Tags | CPython 3.13 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
196ce33c5c5acb975343741dbee80d07615cea0521ea3b0af48bc4beeaf3c645
|
|
BLAKE2b-256 checksum How to use checksums |
484a7afe77e02d9f20de4eba64d54af1bb0f4ae2493cb623b9aaaee0057c861a
|
| 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 Aug 13, 2026.
Transparency logRelease files / pybufarrow-0.1.0-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | pybufarrow-0.1.0-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 20.4 MB |
| Tags | CPython 3.12 Linux glibc 2.17+ ARM64 |
|
SHA-256 checksum How to use checksums |
263a4e25302e4c741a0eed8a99cd9c60969b777f91f2f9e58f12d46507992f52
|
|
BLAKE2b-256 checksum How to use checksums |
2897ca71b8b982c281611551d3be15d1a9b087926e0279d1548ac9f1a7d7fbb3
|
| 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 Aug 13, 2026.
Transparency logRelease files / pybufarrow-0.1.0-cp312-cp312-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | pybufarrow-0.1.0-cp312-cp312-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 23.0 MB |
| Tags | CPython 3.12 Linux glibc 2.17+ x86-64 Linux glibc 2.5+ x86-64 |
|
SHA-256 checksum How to use checksums |
bc0db9ba4c7778457106b2710ebce7e4d140a374f161143a5cd95e7b2cc7f3dd
|
|
BLAKE2b-256 checksum How to use checksums |
73aaea91e0483fb301ca0f1e029d597d942d094e8a8001f5cd2a2a02d90ff6ec
|
| 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 Aug 13, 2026.
Transparency logRelease files / pybufarrow-0.1.0-cp312-cp312-macosx_11_0_arm64.whl
| Download URL | pybufarrow-0.1.0-cp312-cp312-macosx_11_0_arm64.whl |
|---|---|
| Size | 11.0 MB |
| Tags | CPython 3.12 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
8a92ef0c414ff6b6ae9193982a91531fd5cc4f3f397712f0fa66169d3c68bcc7
|
|
BLAKE2b-256 checksum How to use checksums |
216549b15c3f6ccd6b5232b74c61502de1d9750e916fd15eab768de622b8ba93
|
| 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 Aug 13, 2026.
Transparency logRelease files / pybufarrow-0.1.0-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | pybufarrow-0.1.0-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 20.4 MB |
| Tags | CPython 3.11 Linux glibc 2.17+ ARM64 |
|
SHA-256 checksum How to use checksums |
60a5b7a0ddbd0312c09444ed7c91476e817111c3b485d49a82686a7302f0efdd
|
|
BLAKE2b-256 checksum How to use checksums |
c43d1d6905defa743df881be4aab5726f9547a140314b6a05d2a3a42c440254f
|
| 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 Aug 13, 2026.
Transparency logRelease files / pybufarrow-0.1.0-cp311-cp311-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | pybufarrow-0.1.0-cp311-cp311-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 23.0 MB |
| Tags | CPython 3.11 Linux glibc 2.17+ x86-64 Linux glibc 2.5+ x86-64 |
|
SHA-256 checksum How to use checksums |
42db5635f0e27aa95e595befc09a081267d5123eab586e7caeab4112c1f2be17
|
|
BLAKE2b-256 checksum How to use checksums |
0dd7f3f02f31a7a20fc9ddb5cd7e2f0c9594e5b136bae668bc0e60254546536b
|
| 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 Aug 13, 2026.
Transparency logRelease files / pybufarrow-0.1.0-cp311-cp311-macosx_11_0_arm64.whl
| Download URL | pybufarrow-0.1.0-cp311-cp311-macosx_11_0_arm64.whl |
|---|---|
| Size | 11.0 MB |
| Tags | CPython 3.11 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
6df5d5a776036892e97d4330d22d977474436bc1d1288f3d5ffded6b4b0d8bbc
|
|
BLAKE2b-256 checksum How to use checksums |
2bf45527d1d83ec9347866cec931ef2feac62956e17189c149fcf4668bbed87c
|
| 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 Aug 13, 2026.
Transparency logRelease files / pybufarrow-0.1.0-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | pybufarrow-0.1.0-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 20.4 MB |
| Tags | CPython 3.10 Linux glibc 2.17+ ARM64 |
|
SHA-256 checksum How to use checksums |
94071ae4dd25ec808149a09e05b217b9e89c969b1f9b2e269c7f70a9d8d2786e
|
|
BLAKE2b-256 checksum How to use checksums |
9fd198c178629b33bb4a458c3ff55fef7edd38cb889e6357f720ecf83c8409f4
|
| 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 Aug 13, 2026.
Transparency logRelease files / pybufarrow-0.1.0-cp310-cp310-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | pybufarrow-0.1.0-cp310-cp310-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 23.0 MB |
| Tags | CPython 3.10 Linux glibc 2.17+ x86-64 Linux glibc 2.5+ x86-64 |
|
SHA-256 checksum How to use checksums |
2e13fc3035b0242822ed3e3c7c100a3a996ec72606b3a89bd1ad829a319e2500
|
|
BLAKE2b-256 checksum How to use checksums |
b0d23027debfd0ebf245ed3e2798140eddb84bc1f61b24a2acbd613cf11ff3c9
|
| 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 Aug 13, 2026.
Transparency logRelease files / pybufarrow-0.1.0-cp310-cp310-macosx_11_0_arm64.whl
| Download URL | pybufarrow-0.1.0-cp310-cp310-macosx_11_0_arm64.whl |
|---|---|
| Size | 11.0 MB |
| Tags | CPython 3.10 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
d1d9b74b3f9e130f2866cc6692212f57cf197aaee6406a756c606a8283f15937
|
|
BLAKE2b-256 checksum How to use checksums |
1b7b62acb4a0782d71c39fcb4e1d7f4aeb1dd3f73cb83e9c19fd4bb48473f27f
|
| 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 Aug 13, 2026.
Transparency logRelease files / pybufarrow-0.1.0-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | pybufarrow-0.1.0-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 20.4 MB |
| Tags | CPython 3.9 Linux glibc 2.17+ ARM64 |
|
SHA-256 checksum How to use checksums |
3dc3bd05818e35cd7923c94d43d7c650a626c6a008f0dd77fc76d87c1f65dd45
|
|
BLAKE2b-256 checksum How to use checksums |
9d793d39fff5062c526d5f169cbf10ac8ed9c0d0072c8d636371e0ac131859c2
|
| 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 Aug 13, 2026.
Transparency logRelease files / pybufarrow-0.1.0-cp39-cp39-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | pybufarrow-0.1.0-cp39-cp39-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 23.0 MB |
| Tags | CPython 3.9 Linux glibc 2.17+ x86-64 Linux glibc 2.5+ x86-64 |
|
SHA-256 checksum How to use checksums |
7f93b7a7fbd889f76d9ffbdeefdd34e9456949c1b030c198a8f64a02dfdca219
|
|
BLAKE2b-256 checksum How to use checksums |
b7757c4342d338b4f99908f27af2f5e1fd66793996df30bcd04c938e716512e1
|
| 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 Aug 13, 2026.
Transparency logRelease files / pybufarrow-0.1.0-cp39-cp39-macosx_11_0_arm64.whl
| Download URL | pybufarrow-0.1.0-cp39-cp39-macosx_11_0_arm64.whl |
|---|---|
| Size | 11.0 MB |
| Tags | CPython 3.9 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
26eb6d055bda6c815dbef923d9fb7032ac50474a960dbfbe20b1fb1dbb6fab42
|
|
BLAKE2b-256 checksum How to use checksums |
ad6a454c4dd9d7c592c7896b886423ef6518cb1dea42ff99bce6e87bc9c2b36f
|
| 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 Aug 13, 2026.
Transparency log