adiboupk

Python dependency isolation for multi-module projects. Written in C++ for ~1ms startup overhead.

---

The Problem

When a project contains multiple Python modules each with their own requirements.txt, a global pip install causes version conflicts — the last install wins, silently breaking other modules.

project/
├── Enrichments/
│   ├── script1.py
│   └── requirements.txt    ← requests==2.28.0
├── Responses/
│   ├── script2.py
│   └── requirements.txt    ← requests==2.32.5

script1.py expects requests 2.28.0 but gets 2.32.5 (or vice versa).

The Solution

adiboupk creates an isolated venv per group of scripts and transparently routes each execution to the correct environment.

graph LR
    A[adiboupk run script1.py] --> B{Which group?}
    B -->|Enrichments| C[".venvs/Enrichments/"]
    B -->|Responses| D[".venvs/Responses/"]
    C --> E["python script1.py<br/>requests==2.28.0"]
    D --> F["python script2.py<br/>requests==2.32.5"]

Quick Start

# 1. Install
curl -sSL https://raw.githubusercontent.com/NoahPodcast/adiboupk/main/install.sh | bash

# 2. Initialize the project
cd my-project/
adiboupk setup

# 3. Run a script
adiboupk run ./Enrichments/cortex_lookup.py hostname123

That's it. Each script automatically uses the correct dependencies.

Features

Feature	Description
Group isolation	One venv per directory/module
Package isolation	Each package in its own directory
Lock file	Reinstall only when requirements.txt changes
Audit	Detect conflicts across groups
Self-update	adiboupk upgrade to update itself
Cross-platform	Linux and Windows from the same codebase
Fast	Native C++ binary, ~1ms overhead

Integration

Simply replace python with adiboupk run in your orchestration scripts:

// Before — global python, version conflicts
var cmd = 'python ./Enrichments/cortex_lookup.py ' + hostname;

// After — isolated venv per group
var cmd = 'adiboupk run ./Enrichments/cortex_lookup.py ' + hostname;