What Are the LoopX Dependencies? Understanding the Zero-Runtime-Dependency Framework

LoopX has zero runtime dependencies and operates entirely on the Python standard library, requiring only Python 3.11 or higher to run.

The huangruiteng/loopx repository is designed as a lightweight control-plane framework that deliberately avoids external packages. This guide examines the dependency structure declared in pyproject.toml and verifies through source code analysis that no third-party imports exist in the core codebase.

Runtime Dependencies in pyproject.toml

According to the source code in huangruiteng/loopx, the project explicitly declares an empty dependency list for runtime usage. In pyproject.toml, the project metadata contains:

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

This configuration means you can install LoopX in production environments without pulling in any external wheels. The framework implements all control-plane functionality using only Python's built-in modules, making it ideal for restricted environments where dependency management is strictly controlled.

Development and Test Dependencies

While the core framework has no runtime requirements, the repository includes optional development dependencies under the test extra. These packages are only installed when explicitly requested and are not required to run LoopX applications.

The test extra includes the following version-constrained packages:

• 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 tools support the project's test suite, code coverage, linting, and type checking workflows. They remain completely optional for production deployments.

Source Code Verification

You can verify the zero-dependency claim by examining the core source files, which contain no third-party import statements.

In loopx/__init__.py, the package exposes its public API using only standard library components. Similarly, loopx/entrypoint.py implements the loopx console script without requiring external packages. Even extension modules like loopx/extensions/manifest.py register metadata using pure Python constructs.

This design pattern ensures that every module in the core package tree remains free of external dependencies, confirming the pyproject.toml declaration.

Installation Examples

Installing LoopX requires no additional packages beyond the source distribution itself.

To install the base package:

pip install loopx

After installation, you can immediately use the CLI entry point:

loopx --help

To install the optional development dependencies for running the test suite:

pip install "loopx[test]"

Then execute the tests with:

pytest -vv

Summary

• LoopX dependencies are zero at runtime, with an empty dependencies array in pyproject.toml
• The framework requires only Python 3.11+ and uses exclusively standard library modules
• Optional test extras include pytest, jsonschema, ruff, and mypy for development workflows
• Core files including loopx/__init__.py and loopx/entrypoint.py verify the absence of third-party imports
• Install with pip install loopx for production, or pip install "loopx[test]" for development

Frequently Asked Questions

Does LoopX require any external packages to run?

No, LoopX requires zero external packages for runtime operation. The pyproject.toml file explicitly declares dependencies = [], and all core functionality in loopx/__init__.py and loopx/entrypoint.py uses only the Python standard library.

What Python version does LoopX support?

LoopX requires Python 3.11 or higher. This version requirement is specified in the project metadata, though the code relies solely on standard library features available in that release.

How do I run the LoopX test suite?

Install the optional test dependencies using pip install "loopx[test]", which pulls in pytest>=8,<9 and related tools. Then execute pytest -vv to run the full test suite. These dependencies are not required for production usage.

Are LoopX extensions also dependency-free?

Yes, optional extensions such as the Lark provider or OpenViking semantic-preference provider are bundled as entry-points and also rely only on the standard library. They do not declare additional install_requires entries in the package metadata.

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