lpip

Git-backed, name-oriented front end to pip for internal Python packages — no internal PyPI registry required.

Install from PyPI as esys-lpip (pip install esys-lpip); the command and import remain lpip.

Status

What this is

lpip (local-pip) resolves a logical package name from a TOML catalog (lpip-sources.toml), validates configuration and prerequisites, and delegates installation to python -m pip install .... The catalog may be a local file or a Git-backed checkout in a persistent user cache.

It is a small client, not a package manager replacement, registry, or service (ADR-0001, ADR-0004).

Non-goals (v1)

• Internal package index or hosted registry
• A dependency resolver other than pip
• Background daemons, lockfile solving, or workspace orchestration

Quick start

The installable CLI is not available yet. After clone:

python -m venv .venv
# Windows: .venv\Scripts\activate
# Unix: source .venv/bin/activate
pip install -e ".[dev]"
pytest

Re-run scripts/setup-dev after clone if you need pre-commit and gitlint hooks (see docs/workflow/adoption.md).

Intended configuration

Local catalog:

[source]
type = "file"
path = "~/company/lpip-sources.toml"

Git-backed catalog:

[source]
type = "git"
url = "ssh://git.company/dev/lpip-catalog.git"
revision = "main"
path = "lpip-sources.toml"
refresh = "auto"

Example catalog entry:

[packages.libfoo]
url = "git+ssh://git.company/libs/libfoo.git"
revision = "main"
subdirectory = "python"

Intended commands (not implemented): lpip install, lpip list, lpip show, lpip validate, lpip doctor, lpip catalog …, lpip config … (including config init). Details: docs/architecture/cli-and-configuration.md.

Documentation

License

MIT (pyproject.toml).