UTC :: --:--:-- RUST :: stable :: 1.96.0 CLIENT :: browser :: detecting PYPI :: status :: operational CLIENT :: AWS/REGION :: us-east-2 LINUX :: stable_kernel :: 7.0.10 CLOUDFLARE :: pages :: degraded_performance NODE :: lts :: 24.16.0 CLIENT :: os :: detecting CRATES.IO :: crates :: 275k+ GITHUB :: actions :: operational CLIENT :: ip :: masked PYTHON :: stable :: 3.14.x UTC :: --:--:-- RUST :: stable :: 1.96.0 CLIENT :: browser :: detecting PYPI :: status :: operational CLIENT :: AWS/REGION :: us-east-2 LINUX :: stable_kernel :: 7.0.10 CLOUDFLARE :: pages :: degraded_performance NODE :: lts :: 24.16.0 CLIENT :: os :: detecting CRATES.IO :: crates :: 275k+ GITHUB :: actions :: operational CLIENT :: ip :: masked PYTHON :: stable :: 3.14.x
docs::litlaunch :: Start
~/docs/litlaunch/docs/installation.md

Installation

LitLaunch Docs

./view_on_github
repo
Lattice-Foundry/LitLaunch
path
docs/installation.md
ver
1.0.0rc6
commit
cf08bca4c4
synced
May 29, 2026, 03:35 AM UTC

Source Checkout

For development:

git clone https://github.com/Lattice-Foundry/LitLaunch
cd LitLaunch
python -m pip install -e .[dev]

Rerun the editable install after changing package versions or build metadata. Editable-install metadata is generated during installation, so stale local metadata can make importlib.metadata.version("litlaunch") report an older version than litlaunch.__version__ until the package is reinstalled.

Run checks:

python -m pytest
python -m ruff check .
python -m ruff format --check .
python scripts/check_release.py

Package Install

After publication:

python -m pip install litlaunch

Verify the CLI entry points:

litlaunch --help
python -m litlaunch --help

The module form is useful when the environment can import LitLaunch but the console script directory is not on PATH.

Python Versions

The local development environment currently uses Python 3.14.5. Package metadata allows Python 3.10 and newer. CI currently checks Python 3.10 through 3.14 on Windows, Linux, and macOS. Windows and Linux receive first-party manual validation; macOS behavior has limited validation until community testing expands.

Do not assume packaged-app behavior has been validated unless the integration notes for that packaging path say so.