Skip to main content
Yanked

This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
Reason given by maintainers: Distribution paused by the project owner.

Native

The native/ package owns AIRunner's Python launcher entry point, runtime layout helpers, and the pinned llama.cpp / whisper.cpp sidecar support.

AIRunner is a Python application. There is no compiled C++ launcher and no bundle/installer packaging; the desktop app runs directly from the installed Python packages.

flowchart LR
	Python[airunner_native launcher] --> GUI[src/ desktop app]
	Python --> Services[services/ daemon entry points]
	Services --> Sidecars[llama.cpp and whisper.cpp sidecars]
	Python --> RuntimeLayout[runtime layout helpers]
	Python --> Scripts[scripts/ tooling]

What This Package Owns

  • the airunner-native launcher entry point provided by airunner_native (the GUI package owns the primary airunner command; issue #2042)
  • repo and runtime layout helpers (repo_paths, linux_bundle_layout)
  • startup environment and early torch/allocator configuration
  • repo-local support for pinned llama.cpp and whisper.cpp sidecars

Importable native code lives under native/src/airunner_native/.

The architecture audit and package map are tracked in docs/architecture/architecture-complexity-audit.md and docs/architecture/layered_product_architecture.md.

Installation

AIRunner is installed as Python packages:

# repo-local developer install
./scripts/install.sh

# distributed daemon and GUI-client install
./deployment/install_distributed.sh --role daemon
./deployment/install_distributed.sh --role gui-client

For isolated native tooling work in a checkout, install the split package stack first and then install native/ in editable mode:

python -m venv venv
source venv/bin/activate
pip install --upgrade pip setuptools wheel
pip install -e ./services
pip install -e ./native[development]

Test Running

Native changes are validated through the launcher smoke path (the Python launcher entry point) plus the daemon-backed functional suites that consume the built sidecars:

./scripts/install.sh --help
./deployment/install_distributed.sh --help
./scripts/build_runtime_sidecars.sh --target-platform linux
./venv/bin/python -m pytest services/tests/test_llm_functional.py -v --timeout=900
./venv/bin/python -m pytest services/tests/test_stt_transcribe_functional.py -v --timeout=1200

Use the package split contract in docs/architecture/package_split_contract.md when a launcher or installer change affects the wider package matrix.

Metadata

Release files for airunner-native 6.1.3

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

Source distribution (sdist)

Source distribution for airunner-native 6.1.3
File Size Uploaded Provenance Actions
airunner_native-6.1.3.tar.gz 14.4 kB Without provenance Details for airunner_native-6.1.3.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for airunner-native 6.1.3
File Interpreter ABI Platform Actions
airunner_native-6.1.3-py3-none-any.whl Python 3 none any Details for airunner_native-6.1.3-py3-none-any.whl

Total release size: 27.1 kB

Release files / airunner_native-6.1.3.tar.gz

Download URL airunner_native-6.1.3.tar.gz
Size 14.4 kB
Tags Source
SHA-256 checksum
How to use checksums
5bbb676783e6f7a747d8fe88cd33bd03321d3042e8ca6aa5ae6235c15acba999
BLAKE2b-256 checksum
How to use checksums
42dbd8384b881a1647e8dd8fce95f31bcd45d7d9cf4cfcc0b94c08ee40e9e8b7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.9.25

Release files / airunner_native-6.1.3-py3-none-any.whl

Download URL airunner_native-6.1.3-py3-none-any.whl
Size 12.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
4ea6d86a283498367fb80bceada5d07abfef6fa3cc0c8cc1097bb7334ba95f37
BLAKE2b-256 checksum
How to use checksums
4dc0347520fb9b29e9bd3e0a377087a119d710e653bccdda3ad013c898fd3940
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.9.25

Security for airunner-native 6.1.3

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.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A 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.

Release history Release notifications | RSS feed

This release

6.1.3 This release

2 release files No provenance

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