agi-app-polars-execution
agi-app-polars-execution publishes the execution_polars_project AGILAB app
as a self-contained PyPI payload. It mirrors the Pandas execution example with a
Polars worker path.
Purpose
Use this package to compare AGILAB execution behavior on a deterministic tabular workload while using Polars for the processing step. It is useful when you want native dataframe performance without changing the surrounding AGILAB manager/worker contract.
Installed Project
The distribution name is agi-app-polars-execution; the AGILAB project name is
execution_polars_project. The package exposes both execution_polars and
execution_polars_project through the agilab.apps entry point group, so
AgiEnv(app="execution_polars_project") works without a monorepo checkout.
Install
pip install agi-app-polars-execution
Most users get this package through agi-apps, agilab[ui], or
agilab[examples]; direct installation is useful when validating one app
package in isolation.
Run In AGILAB
Select execution_polars_project, open ORCHESTRATE, then run Deploy scheduler & workers and
RUN. Start locally, then compare the output with
execution_pandas_project if you want an engine-level contrast.
Expected Inputs
The default run creates its own deterministic CSV workload under shared storage. No external dataset, cloud account, notebook, or API key is required.
Expected Outputs
Workers write processed CSV or Parquet outputs and the reducer writes a summary with row counts, source files, engine labels, score metrics, and execution metadata.
Change One Thing
Change the partition count or output format, then compare the reducer summary against a Pandas run. The point is to change the engine while keeping the workflow contract stable.
Scope
This is a synthetic execution-path example. It is useful for validating Polars worker behavior, not for demonstrating a domain analytics product.
Metadata
Release files for agi-app-polars-execution 2026.11.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| agi_app_polars_execution-2026.11.2.tar.gz | 17.0 kB | With provenance | Details for agi_app_polars_execution-2026.11.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| agi_app_polars_execution-2026.11.2-py3-none-any.whl | Python 3 | none | any | Details for agi_app_polars_execution-2026.11.2-py3-none-any.whl |
Total release size: 38.2 kB
Release files / agi_app_polars_execution-2026.11.2.tar.gz
| Download URL | agi_app_polars_execution-2026.11.2.tar.gz |
|---|---|
| Size | 17.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
11b41eeb797be3553c3907260033e3564d44898d477a5f8638750ba9feda5ab0
|
|
BLAKE2b-256 checksum How to use checksums |
3f3a8eed72a7887e7af6b7289b086a665c80d6256fe43bf6b4147c16ce92f6d9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 2, 2026.
Transparency logRelease files / agi_app_polars_execution-2026.11.2-py3-none-any.whl
| Download URL | agi_app_polars_execution-2026.11.2-py3-none-any.whl |
|---|---|
| Size | 21.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0314d71ea2022023283f0516f5128d0ac6db0302606af2d643afbb66ba6293fc
|
|
BLAKE2b-256 checksum How to use checksums |
d4a18dd44d540bee618c96756a99d7a0bab38c66e19e5ccaee0c730efe8ae6eb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 2, 2026.
Transparency logSecurity for agi-app-polars-execution 2026.11.2
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for agi_app_polars_execution-2026.11.2.tar.gz
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 Nov 2, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.