Skip to main content

allye_data_connector

allye_data_connector is a local connector that lets you exchange pandas.DataFrame objects between Python and Allye widgets.

It works by appending events to a line-delimited manifest file (manifest.jsonl) and storing the actual Arrow payload either in:

  • OS shared memory (fast, for smaller data), or
  • a memory-mappable file on disk (for larger data).

Installation

From PyPI:

pip install allye_data_connector

From source (development):

pip install -e .

If you haven't installed Allye yet, please download and install it from here.

Quickstart

Send a DataFrame to Allye Canvas:

import pandas as pd
import seaborn as sns

import allye_data_connector
df = sns.load_dataset("iris")
allye_data_connector.send_dataframe(df, table_name='iris')

Use Allye's Allye Data Receiver widget to receive the dataframe data and perform visualizations.

Allye Data Receiver

Get Data from Canvas / Read it back:

Use Allye's Allye Data Transmitter widget to send Allye data, receive it on the Jupyter side, and execute subsequent processing.

Allye Data Transmitter

df = allye_data_connector.get_dataframe('iris_setosa_versicolor')
df.head()

List available tables:

tables = adc.list_tables()
for t in tables:
    print(t["table_name"], t["transport"], t["shape"])

How it works (high level)

  1. send_dataframe() appends a status="writing" event to manifest.jsonl.
  2. The DataFrame is serialized to Apache Arrow:
    • transport="auto" uses shared memory when the payload is below max_shm_bytes
    • otherwise it falls back to writing Arrow IPC files under payloads/ (chunked by chunk_rows)
  3. A final status="ready" event is appended with a payload reference (transport + locator).
  4. get_dataframe() scans the manifest for the latest status="ready" entry matching table_name (and optional producer), then loads the Arrow payload back into a DataFrame.

Features

  • Send/receive DataFrames with send_dataframe() and get_dataframe()
  • Local, file-based coordination via manifest.jsonl (append-only)
  • Automatic transport selection (transport="auto") based on size
  • Optional TTL + garbage collection for payload cleanup (gc())
  • Producer filtering (e.g., read only entries produced by Allye widgets)

Cleanup (optional)

If you send with ttl_sec=..., the payload gets an expiration timestamp. You can remove expired payloads with:

adc.gc(dry_run=False)

gc(dry_run=True) (default) only reports what would be removed.

Notes

  • This is a local IPC-oriented connector; it does not do networking or authentication.
  • Very large DataFrames may exceed OS shared memory limits; the implementation automatically falls back to disk-backed Arrow files.

Release files for allye-data-connector 0.1.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for allye-data-connector 0.1.2
File Size Uploaded
allye_data_connector-0.1.2.tar.gz 14.2 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for allye-data-connector 0.1.2
File Interpreter ABI Platform
allye_data_connector-0.1.2-py3-none-any.whl Python 3 none any Details

Total release size: 29.0 kB

Release files / allye_data_connector-0.1.2.tar.gz

Download URL allye_data_connector-0.1.2.tar.gz
Size 14.2 kB
Tags Source
SHA-256 checksum
How to use checksums
fa12b4e702cd4f69501805e37744a851c10ef5aa6da993de91ddaed03b299e55
BLAKE2b-256 checksum
How to use checksums
eed6b08c74c33714aa557f7a61e421c9cf972b5b892b9ac601c9e6150e470e31
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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 Jan 4, 2026.

Transparency log

Release files / allye_data_connector-0.1.2-py3-none-any.whl

Download URL allye_data_connector-0.1.2-py3-none-any.whl
Size 14.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
ce6c4e106a6d366576c4b6279559f54d79aae10b4488d1f5268477874b6ed9ba
BLAKE2b-256 checksum
How to use checksums
831cbf271e81eff6eba10b68e4e857d5cdcdc5275ea9083d867e4141823b70e2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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 Jan 4, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.2 This release

2 release files

0.1.1

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page