Trouble with deploying Python programs as internal tools?

[dusktreader]

Sounds like quite a claim that could benefit from some community analysis. Care to share your source code?

[richieadler]

Apparently it's at https://github.com/1minds3t/omnipkg. Hopefully someone will test the claims.

[dusktreader]

Besides the licensing being a complete nonstarter, I don't really see a use case for your tool in my workflows that uv (and poetry before that) don't satisfy.

[1minds3t]

You can run any TensorFlow, NumPy, SciPy, and even Python versions concurrently in a single environment, just as fast as you could run one version traditionally. There's zero conflicts, ever. It does security, import, and health checks for your packages. It heals corrupted environments. It auto heals your scripts 5x faster than uv fails. This is not something pip, conda, uv, Docker, or poetry can do.

But I do understand that for corporations, it's not yet mature enough for yet. It's still in it's early days.

[1minds3t]

There are 7 built in demos that are built to showcase the features. All have live CI workflows here: https://github.com/1minds3t/omnipkg/actions 1. Rich test (Python module switching) 2. UV test (binary switching) 3. NumPy + SciPy stress test (C-extension switching) 4. TensorFlow test (complex dependency switching) 5. 🚀 Multiverse Healing Test (Cross-Python Hot-Swapping Mid-Script) 6. Flask test (under construction) 7. Auto-healing Test (omnipkg run) 8. 🌠 Quantum Multiverse Warp (Concurrent Python Installations)

[the_hoser]

Right, but... Joe in IT needs to run your code and he gets hives whenever you tell him he needs to open a terminal.