One environment. Infinite Python and package versions. Zero conflicts.
omnipkg is not just another package manager. It's an intelligent, self-healing runtime orchestrator that breaks the fundamental laws of Python environments. For 30 years, developers accepted that you couldn't run multiple Python versions in one script, or safely switch C-extensions like NumPy mid-execution. Omnipkg proves this is no longer true.
Born from a real-world nightmare—a forced downgrade that wrecked a production environment—omnipkg was built to solve what others couldn't: achieving perfect dependency isolation and runtime adaptability without the overhead of containers or multiple venvs.
Multi-version installation tests run hourly. Live results here.
The Multi-Version Nightmare is Over: Modern projects are messy. You need tensorflow==2.10 for a legacy model but tensorflow==2.15 for new training. A critical library requires numpy==1.21 while your latest feature needs numpy==2.0. Traditional solutions like Docker or virtual environments force you into a painful choice: duplicate entire environments, endure slow context switching, or face crippling dependency conflicts.
The Multi-Interpreter Wall is Gone: Legacy codebases often require older Python versions (e.g., Django on 3.8) while modern ML demands the latest (Python 3.11+). This forces developers to constantly manage and switch between separate, isolated environments, killing productivity.
The omnipkg Solution: One Environment, Infinite Python Versions & Packages, Zero Conflicts, Downtime, or Setup. Faster than UV.
omnipkg doesn't just solve these problems—it makes them irrelevant.
- Run Concurrently: Execute tests for Python 3.9, 3.10, and 3.11 at the same time, from one command, test is done in under 500ms. No more sequential CI jobs.
- Switch Mid-Script: Seamlessly use
torch==2.0.0andtorch==2.7.1in the same script without restarting. - Instant Healing: Recover from environment damage in microseconds, not hours.
- Speak Your Language: All of this, in your native tongue.
This is the new reality: one environment, one script, everything just works.
Our "Quantum Multiverse Warp" demo, validated live in our CI, executes a single script across three different Python interpreters and three package versions concurrently in the same environment. The results are not just fast; they redefine what's possible for CI/CD.
| Task (Same Script, Same Environment) | Execution Time |
|---|---|
| 🧵 Thread 1: Python 3.9 + Rich 13.4.2 | ✅ 579.6ms |
| 🧵 Thread 2: Python 3.10 + Rich 13.6.0 | ✅ 548.4ms |
| 🧵 Thread 3: Python 3.11 + Rich 13.7.1 | ✅ 571.8ms |
| 🏆 Total Concurrent Runtime | 580.1ms |
This isn't just a speedup; it's a paradigm shift. What traditionally takes minutes with Docker or complex venv scripting, omnipkg accomplishes in under 600 milliseconds. This isn't a simulation; it's a live, production-ready capability for high-performance Python automation.
Don't believe it? See the live proof, then run Demo 8 to experience it yourself.
uv pip install omnipkg && omnipkg demo
**Live CI Output from Multiverse Analysis:**
```bash
🚀 Launching multiverse analysis from Python 3.11…
📦 Step 1: Swapping to Python 3.9…
🐍 Active interpreter switched in <1 second!
✅ All dependencies auto-healed
- NumPy 1.26.4
- SciPy 1.13.1
🧪 SciPy result: 225
📦 Step 2: Swapping back to Python 3.11…
🐍 Hot-swapped Python interpreter instantly
✅ TensorFlow 2.20.0 ready to go
🧪 TensorFlow prediction: SUCCESS
🌀 SAFETY PROTOCOL: Returned to original Python 3.11 environmentKey Achievement: Total test runtime only ~10 seconds for complete multiverse analysis, with automatic healing when NumPy compatibility issues arise. Interpreter swaps finish in just 0.25 seconds!
omnipkg is the first tool that actively repairs your environment while you work.
omnipkg run: Our intelligent script runner detectsModuleNotFoundError,AssertionError(for version conflicts), and even NumPy C-extension failures. It then automatically creates and activates a version-specific "bubble" to heal the script, often completing the entire process faster than other tools take to simply fail.- The Ghost Hunter: On every startup,
omnipkgproactively scans all managedsite-packagesfor corrupted installations (e.g.,~temp-name.dist-info) left behind by failedpipinstalls and surgically removes them, preventing environment rot before it starts.
Live CI Output from Auto-Healing:
⏱️ UV run failed in: 5379.237 ms (5,379,236,666 ns)
🔍 NumPy 2.0 compatibility issue detected. Auto-healing with numpy downgrade...
- Downgrading to numpy<2.0 for compatibility
✅ Using bubble: numpy-1.26.4
🚀 Re-running with omnipkg auto-heal...
✅ Script completed successfully inside omnipkg bubble.
======================================================================
🚀 PERFORMANCE COMPARISON: UV vs OMNIPKG
======================================================================
UV Failed Run: 5379.237 ms (5,379,236,666 ns)
omnipkg Healing: 693.212 ms ( 693,211,844 ns)
----------------------------------------------------------------------
🎯 omnipkg is 7.76x FASTER than UV!
💥 That's 675.99% improvement!
======================================================================
Switch package versions mid-script using omnipkgLoader, without restarting or changing environments. omnipkg seamlessly juggles C-extension packages like numpy and scipy in the same Python process. The loader even handles complex nested dependency contexts, a feat unmatched by other tools.
Example Code:
from omnipkg.loader import omnipkgLoader
from omnipkg.core import ConfigManager # Recommended for robust path discovery
config = ConfigManager().config # Load your omnipkg config once
with omnipkgLoader("numpy==1.24.3", config=config):
import numpy
print(numpy.__version__) # Outputs: 1.24.3
import numpy # Re-import/reload might be needed if numpy was imported before the 'with' block
print(numpy.__version__) # Outputs: Original main env version (e.g., 1.26.4)Key CI Output Excerpts (Nested Loaders):
--- Nested Loader Test ---
🌀 Testing nested loader usage...
✅ Outer context - Typing Extensions: 4.5.0
🌀 omnipkg loader: Activating tensorflow==2.13.0...
✅ Inner context - TensorFlow: 2.13.0
✅ Inner context - Typing Extensions: 4.5.0
✅ Nested loader test: Model created successfully
omnipkg eliminates language barriers with advanced AI localization supporting 24+ languages, making package management accessible to developers worldwide in their native language.
Key Features: Auto-detection from system locale, competitive AI translation models, context-aware technical term handling, and continuous self-improvement from user feedback.
# Set language permanently
omnipkg config set language zh_CN
# ✅ Language permanently set to: 中文 (简体)
# Temporary language override
omnipkg --lang es install requests
# View current configuration
cat ~/.config/omnipkg/config.jsonZero setup required—works in your language from first run with graceful fallbacks and clear beta transparency.
omnipkg automatically reorders installations and isolates conflicts, preventing environment-breaking downgrades.
Example: Conflicting torch versions:
omnipkg install torch==2.0.0 torch==2.7.1What happens? omnipkg reorders installs to trigger the bubble creation, installs torch==2.7.1 in the main environment, and isolates torch==2.0.0 in a lightweight "bubble," sharing compatible dependencies to save space. No virtual environments or containers needed.
🔄 Reordered: torch==2.7.1, torch==2.0.0
📦 Installing torch==2.7.1... ✅ Done
🛡️ Downgrade detected for torch==2.0.0
🫧 Creating bubble for torch==2.0.0... ✅ Done
🔄 Restoring torch==2.7.1... ✅ Environment secure
omnipkg goes beyond simple version tracking, building a deep knowledge base (in Redis or SQLite) for every package. In v1.5.0, this now includes live import validation during bubble creation.
- The Problem: A package can be "installed" but still be broken due to missing C-extensions or incorrect
sys.pathentries. - The Solution: When creating a bubble,
omnipkgnow runs an isolated import test for every single dependency. It detects failures (e.g.,absl-py: No module named 'absl_py') and even attempts to automatically repair them, ensuring bubbles are not just created, but are guaranteed to be functional.
Example Insight:
omnipkg info uv
📋 KEY DATA for 'uv':
🎯 Active Version: 0.8.11
🫧 Bubbled Versions: 0.8.10
---[ Health & Security ]---
🔒 Security Issues : 0
🛡️ Audit Status : checked_in_bulk
✅ Importable : True| Intelligence Includes | Redis/SQLite Superpowers |
|---|---|
| • Binary Analysis (ELF validation, file sizes) | • 0.2ms metadata lookups |
| • CLI Command Mapping (all subcommands/flags) | • Compressed storage for large data |
| • Security Audits (vulnerability scans) | • Atomic transaction safety |
| • Dependency Graphs (conflict detection) | • Intelligent caching of expensive operations |
| • Import Validation (runtime testing) | • Enables future C-extension symlinking |
If an external tool (like pip or uv) causes damage, omnipkg revert restores your environment to a "last known good" state in seconds.
Key CI Output Excerpt:
Initial uv version (omnipkg-installed):uv 0.8.11
$ uv pip install uv==0.7.13
- uv==0.8.11
+ uv==0.7.13
uv self-downgraded successfully.
Current uv version (after uv's operation): uv 0.7.13
⚖️ Comparing current environment to the last known good snapshot...
📝 The following actions will be taken to restore the environment:
- Fix Version: uv==0.8.11
🚀 Starting revert operation...
✅ Environment successfully reverted to the last known good state.
--- Verifying UV version after omnipkg revert ---
uv 0.8.11UV is saved, along with any deps!
omnipkg works out of the box with automatic SQLite fallback when Redis isn't available. Redis is optional for enhanced performance.
Ready to end dependency hell? uv pip install omnipkg && omnipkg demo to see the magic in under 30 seconds.
Available via UV, pip, conda-forge, Docker, brew, Github, and piwheels, support for Linux, Windows, Mac, and Rasperry Pi
uv pip install omnipkg
pip install omnipkg
# Easiest guaranteed way
conda install -c conda-forge omnipkg
# Or with mamba if you prefer speed
mamba install -c conda-forge omnipkg
conda install -c minds3t omnipkg
# Or with mamba
mamba install -c minds3t omnipkg
# Pull from Docker Hub
docker pull 1minds3t/omnipkg:latest
# Pull from GitHub Container Registry (GHCR)
docker pull ghcr.io/1minds3t/omnipkg:latest# Add the tap first
brew tap 1minds3t/omnipkg
# Install omnipkg
brew install omnipkg
For users on Raspberry Pi, you can use the optimized wheels from piwheels for faster installation.
pip install --index-url=https://www.piwheels.org/simple/ omnipkg# Clone the repo
git clone https://github.com/1minds3t/omnipkg.git
cd omnipkg
# Install in editable mode (optional for dev)
pip install -e .omnipkg demoChoose from:
- Rich test (Python module switching)
- UV test (binary switching)
- NumPy + SciPy stress test (C-extension switching)
- TensorFlow test (complex dependency switching)
- 🚀 Multiverse Healing Test (Cross-Python Hot-Swapping Mid-Script) Flask test (under construction)
- Auto-healing Test (omnipkg run)
- 🌠 Quantum Multiverse Warp (Concurrent Python Installations)
# Let omnipkg manage your native Python automatically
omnipkg status
# 🎯 Your native Python is now managed!
# See available interpreters
omnipkg info python
# Install a new Python version if needed (requires Python >= 3.10)
omnipkg python adopt 3.10
# Hot-swap your entire shell context
omnipkg swap python 3.10
python --version # Now Python 3.10.xFor maximum performance, install Redis:
-
Linux (Ubuntu/Debian):
sudo apt-get update && sudo apt-get install redis-server sudo systemctl enable redis && sudo systemctl start redis
-
macOS (Homebrew):
brew install redis && brew services start redis -
Windows: Use WSL2 or Docker:
docker run -d -p 6379:6379 --name redis-omnipkg redis
-
Verify Redis:
redis-cli ping(should returnPONG)
- Adopt Interpreters: On first run,
omnipkgautomatically adopts your native Python. Add more withomnipkg python adopt <version>. - Install Packages: Use
omnipkg install uv==0.7.13 uv==0.7.14oromnipkg install -r req.txt - Conflict Detection:
omnipkgspots version clashes and isolates them in bubbles. - Dynamic Package Switching: Use
omnipkgLoaderto switch package versions mid-script. - Interpreter Hot-Swapping: Switch your shell's active Python instantly with
omnipkg swap python <version>. - Intelligence Database: High-performance knowledge base built for all packages (Redis preferred, SQLite fallback).
- Auto-healing:
omnipkg runautomatically fixes compatibility issues in real-time. - Atomic Snapshots: Instant rollback with
omnipkg revert.
Example: Safe Flask-Login Downgrade:
omnipkg install flask-login==0.4.1📸 Taking LIVE pre-installation snapshot...
🛡️ DOWNGRADE PROTECTION ACTIVATED!
-> Detected conflict: flask-login v0.6.3 → v0.4.1
🫧 Creating bubble for flask-login v0.4.1... ✅ Done
🔄 Restoring flask-login v0.6.3... ✅ Environment secureVerify:
omnipkg info flask-login📋 flask-login STATUS:
🎯 Active: 0.6.3 (main)
🫧 Available: 0.4.1 (bubble)
📊 Space Saved: 55.5%You now have both versions available in one environment, ready for use anytime!
Already working in production: Our "Quantum Multiverse Warp" demo proves you can run Python 3.9, 3.10, and 3.11 concurrently in the same script, same environment, in under 6.22 seconds.
Already working in CI: Mid-script interpreter switching now works reliably in automated environments with atomic safety guarantees.
Ensures your bubbles are 100% working and auto heals if they don't.
- Time Machine Technology for Legacy Packages: Install ancient packages with historically accurate build tools and dependencies that are 100% proven to work in any environment.
- 10-100x speedup on I/O operations and concurrent processing
- Memory-safe concurrency for atomic operations at scale
- Zero-copy architecture for massive dependency graphs
- Auto-detect language boundaries and manage cross-stack dependencies
- Unified dependency graph across Python, Node.js, Rust, and system packages
- Smart conflict resolution between language-specific package managers
- Cross-process locking for truly safe concurrent installations
- Distributed transaction support for multi-machine environments
- Crash-proof operation sequencing with guaranteed rollback capabilities
- Transparent uv/conda/pip interoperability with smart fallbacks
- Unified CLI interface across all supported package managers
- Intelligent backend selection based on performance characteristics
Learn more about omnipkg's capabilities:
- Getting Started: Installation and setup.
- CLI Commands Reference: All
omnipkgcommands. - Python Hot-Swapping Guide: Master multi-interpreter switching.
- Runtime Version Switching: Master
omnipkgLoaderfor dynamic, mid-script version changes. - Advanced Management: Redis/SQLite interaction and troubleshooting.
- Future Roadmap: Features being built today - for you!
omnipkg uses a dual-license model designed for maximum adoption and sustainable growth:
- AGPLv3: For open-source and academic use (View License).
- Commercial License: For proprietary systems and enterprise deployment (View Commercial License).
Commercial inquiries: omnipkg@proton.me
This project thrives on community collaboration. Contributions, bug reports, and feature requests are incredibly welcome. Join us in revolutionizing Python dependency management.
Translation Help: Found translation bugs or missing languages? Submit pull requests with corrections or new translations—we welcome community contributions to make omnipkg accessible worldwide.
________________________________________________________________
/ \
| pip: "Version conflicts? New env please!" |
| Docker: "Spin up containers for 45s each!" |
| venv: "90s of setup for one Python version!" |
| |
| omnipkg: *runs 3 Python versions concurrently in 580ms, |
| caches installs in 50ms* |
| |
| "Hold my multiverse—I just ran your entire |
| CI matrix faster than you blinked." |
\________________________________________________________________/
\ ^__^
\ (🐍)\_______
(__)\ )\/\
||----w |
|| ||
~ omnipkg: The Multiverse Package Manager ~