What Are the LoopX Dependencies?

LoopX has zero runtime dependencies and relies entirely on the Python standard library.

The huangruiteng/loopx repository is architected as a lightweight control-plane framework that eliminates external package dependencies entirely. This design choice makes LoopX ideal for environments where minimizing third-party installations is critical.

LoopX Runtime Dependencies (Zero)

The core LoopX package declares no runtime dependencies. This is explicitly codified in pyproject.toml:

[project]
dependencies = []          # ← no packages required at runtime

This empty dependencies array means a standard pip install loopx pulls in absolutely no external wheels. The codebase achieves this by restricting all imports to Python's standard library across every module.

Key source files verify this zero-dependency claim:

• loopx/__init__.py — Exposes the public API with no third-party imports
• loopx/entrypoint.py — Implements the loopx CLI using only stdlib modules
• loopx/extensions/manifest.py — Registers extension metadata without external dependencies

Optional extension providers (such as the Lark provider or OpenViking semantic-preference provider) are bundled as entry-points but similarly declare no additional install_requires entries.

Optional Development Dependencies

While runtime usage requires no external packages, LoopX maintains a test extra for contributors running the test suite and linting tools:

Extra	Packages
test	jsonschema>=4.23,<5 pytest>=8,<9 pytest-cov>=5,<7 pytest-xdist>=3,<4 ruff>=0.12,<0.16 mypy>=1.18,<2

These packages are strictly optional and only install when explicitly requested.

Installation Commands

Install LoopX for production use (no dependencies pulled):

pip install loopx

Install with test dependencies for development:

pip install "loopx[test]"

Verify the CLI works immediately:

loopx --help

Why Zero Dependencies Matter

Choosing a framework with no LoopX dependencies provides several operational advantages:

• Reduced supply chain attack surface — No transitive dependency tree to audit
• Faster container builds — Smaller image sizes without external wheel downloads
• Simpler air-gapped deployments — Standard library suffices for full functionality
• Predictable behavior — No version conflicts or breaking changes from upstream packages

Python Version Requirements

LoopX targets Python 3.11+. This modern baseline provides sufficient standard library capabilities (including improved asyncio support and tomllib for TOML parsing) to implement framework features without external helpers.

Summary

• LoopX declares zero runtime dependencies in pyproject.toml
• The entire codebase uses only Python standard library modules
• Optional test extra provides pytest, mypy, ruff, and related tools for development
• Installation requires only pip install loopx with no additional flags
• Extensions and entry-points maintain the same zero-dependency constraint

Frequently Asked Questions

Does LoopX require any packages to be installed?

No. LoopX operates entirely on the Python standard library. The dependencies = [] declaration in pyproject.toml ensures pip install loopx pulls in zero external packages.

What packages are included in the test extra?

The test extra includes jsonschema, pytest, pytest-cov, pytest-xdist, ruff, and mypy with pinned version ranges. These support linting, type-checking, and test execution during development only.

Can LoopX extensions add their own dependencies?

No. Extension providers bundled with LoopX (such as the Lark or OpenViking providers) are implemented using only standard library imports and do not declare additional install_requires entries.

What Python version does LoopX require?

LoopX requires Python 3.11 or newer. This version provides sufficient standard library functionality to implement all framework features without third-party packages.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}