Omnipkg
Universal Python Runtime Orchestrator - One environment. Infinite Pythons and packages. <1ms zero-copy IPC. On @conda-forge and Docker.
Install / Use
/learn @1minds3t/OmnipkgREADME
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.
<!-- COMPARISON_STATS_START -->
⚖️ Multi-Version Support
Multi-version installation tests run every 3 hours. Live results here.
<!-- COMPARISON_STATS_END -->
💡 Why This Matters
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.
🧠 Revolutionary Core Features
1. Multiverse Orchestration & Python Hot-Swapping 
The "Quantum Multiverse Warp": 3 Pythons, 1 Script, Sub-3ms Execution
Our "Quantum Multiverse Warp" demo, validated live in CI across multiple platforms, executes a single script across three different Python interpreters and three package versions concurrently in the same environment. The hot worker performance isn't just fast; it redefines what's possible for high-performance Python automation.
Production Benchmark Results (macOS CI)
| Task (Same Script, Same Environment) | Hot Worker Execution | | ------------------------------------ | :------------------: | | 🧵 Thread 1: Python 3.9 + Rich 13.4.2 | ✅ 2.2ms | | 🧵 Thread 2: Python 3.10 + Rich 13.6.0 | ✅ 2.3ms | | 🧵 Thread 3: Python 3.11 + Rich 13.7.1 | ✅ 2.3ms | | 🏆 Total Concurrent Runtime | 2.3ms | | ⏱️ Total Test Duration (with setup) | 2.14s |
Platform-Specific Performance:
| Platform | Hot Worker Benchmark | Total w/ Setup | CI Link | |----------|---------------------|----------------|---------| | 🐧 Linux | 3.8ms avg (3.2-4.5ms range) | ~580ms | View CI | | 🍎 macOS | 2.3ms avg (2.2-2.3ms range) | 2.14s | View CI |
What This Actually Means
The numbers that matter are the hot worker benchmarks (sub-5ms). This is the actual execution time for running code across three concurrent Python interpreters with three different package versions. The "Total w/ Setup" includes one-time initialization:
- Worker pool spawning
- Package installation (if not cached)
- Environment validation
Why This Is Revolutionary:
- Traditional approach: Docker containers or separate venvs would take 30-90 seconds minimum to achieve the same multi-version testing
- omnipkg approach: After initial setup, switching between Python versions and package combinations happens in **microseco
Related Skills
node-connect
346.4kDiagnose OpenClaw node connection and pairing failures for Android, iOS, and macOS companion apps
prose
346.4kOpenProse VM skill pack. Activate on any `prose` command, .prose files, or OpenProse mentions; orchestrates multi-agent workflows.
claude-opus-4-5-migration
107.2kMigrate prompts and code from Claude Sonnet 4.0, Sonnet 4.5, or Opus 4.1 to Opus 4.5
frontend-design
107.2kCreate distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
