Next-generation developer infrastructure, SAT resolvers, and hermetic runtimes for Python.
Repository • Quickstart • Feature Guides • Architecture • Releases
Lux Systems Engineering designs and builds high-performance, deterministic developer toolchains. We believe that developer tools should be instantaneous, zero-overhead, memory-safe, and visually clean.
Our flagship project is Lux (lux): an all-in-one Python package and project manager, SAT dependency solver, hermetic runtime orchestrator, and binary ABI bridge written in 100% safe Rust (#![deny(unsafe_code)]).
|
A specialized PubGrub SAT solver resolves package dependencies quickly and deterministically directly in memory. |
In-process binary inspection parses PE ( |
|
Global artifact deduplication ( |
Manage, pin ( |
|
Seamless replacement for |
Execute standalone scripts with PEP 723 inline dependencies ( |
Install Lux with a single command:
powershell -ExecutionPolicy ByPass -c "irm https://raw.githubusercontent.com/Lux-Python/Lux/main/install.ps1 | iex"curl -LsSf https://raw.githubusercontent.com/Lux-Python/Lux/main/install.sh | shInitialize and run a project in seconds:
# Initialize project with pyproject.toml and .venv
lux init my-app
cd my-app
# Or create a standalone virtual environment anywhere
lux venv
# Add dependencies with instant PubGrub SAT resolution
lux add fastapi uvicorn "pydantic>=2.0"
# Run your application in the virtual environment
lux run uvicorn main:app --reloadPubGrub-CDCL SAT Solver Architecture
Lux uses a Conflict-Driven Clause Learning (CDCL) dependency solver designed for package version intervals:
- Unit Propagation: Propagates positive and negative package assignments to minimize decisions.
- Incompatibility Graph: Derives conflict clauses upon encountering unsatisfiable requirement constraints.
- Non-Chronological Backjumping: Backjumps directly to the decision level responsible for the conflict.
- Pure Rust In-Process Execution: Executes directly in-memory without spawning external resolver processes.
Native Binary ABI Inspection (lux doctor)
Compiled C/C++ extensions frequently fail at runtime due to missing dynamic link libraries (e.g. MSVCP140.dll, libgomp.so, libc++.dylib).
lux doctor provides native, zero-copy binary inspection powered by the object crate:
- Inspects PE/COFF, ELF, and Mach-O import headers directly from disk.
- Validates that all imported symbols and shared libraries resolve against the active virtual sysroot (
.venv/sysroot) and system library paths. - Provides immediate diagnostics with actionable resolution paths before running Python.
Content-Addressable Storage (CAS) & Zero-Copy Linking
Lux uses a global CAS directory (~/.lux/cache/cas):
- Wheel archives are downloaded and decompressed directly into content-addressed directories indexed by SHA-256.
- Virtual environment installation uses atomic filesystem hardlinks with copy fallback.
- Disk usage across multiple projects sharing packages is deduplicated.
Our flagship codebase is hosted at Lux-Python/Lux:
lux
├── crates/lux_core # PEP 440, PEP 508, PEP 621, PEP 723, lux.lock, .python-version
├── crates/lux_resolver # PubGrub-CDCL SAT dependency solver
├── crates/lux_cache # CAS store, HTTP/2 range reader, Python runtime manager
├── crates/lux_sysroot # Binary ABI inspector (PE/ELF/Mach-O) & PEP 517 builder
└── crates/lux_cli # Minimalist CLI toolchain & pip interface
- 100% Safe Rust:
#![deny(unsafe_code)]enforced across all workspace crates. - Zero Clippy Warnings: Maintained under
-D clippy::all -D clippy::pedantic -D clippy::nursery. - No Marketing Fluff or Emojis: Strict Cargo/uv design language with right-aligned verbs, microsecond timestamps, and pure box-drawing characters.
- Hermetic Determinism: Cryptographic integrity hashes (SHA-256) on all locked packages.
© 2026 Lux Systems Engineering • Open Source under MIT OR Apache-2.0