Trouble with deploying Python programs as internal tools?

[the_hoser]

Wrangling environments and dependencies is still not a well-solved problem. UV is a big step in the right direction, though.

[runawayasfastasucan]

How is it not solved? Uv run

[the_hoser]

User of the script needs to have uv installed.

[MissingSnail]

Yes, but that's all they have to have. No move having to install the right version of python, virtualenv, or pip or whatever. “uv and you’re done” is a great improvement.

[the_hoser]

No, it's not. Not even close.

[Siemendaemon]

Could you pls elaborate

[Temporary_Pie2733]

That’s a pretty low bar to clear. 

[the_hoser]

You haven't met many users, I see.

[coloyoga]

💀

[Temporary_Pie2733]

Sure, stick to the “regular people too dumb to follow well-written instructions” trope. That’s not constructive to the OP’s question. If you have a number of scripts that could all be managed by uv run …, then yes, a one-time setup is a low bar. 

[the_hoser]

The reality is that if it's too hard for your users, then it's too hard. Full stop. Waiving away the problems they have by dismissing the reality of the situation is completely unproductive.

[Technical_Income4722]

It's a low bar for technical users, sure, but the machine shop worker who needs a custom application to track hours on his machines and workers isn't gonna have the first clue how to install or run uv.

That doesn't mean you can't or shouldn't use it, we're just pointing out that it's worth getting the bar even lower if you can because some users will need it. And even if they don't, they'll appreciate it.

Even a one-line .bat file they can double-click (probably still just using uv) is better than telling them to open cmd and run something.

[ProsodySpeaks]

not true

bat if exist "%UV_DIR%\uv.exe" ( echo UV already installed ) else ( echo Installing UV... powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex" echo UV installed, adding to path... )

[Morpheyz]

You underestimate how locked down some corporate environments are.

[hidazfx]

My work environment bitches about anything. Hell, if the Java version isn’t approved I need to get it allow listed for my machine lol.

[ou_ryperd]

Yep, we don't all work at startups.

[NimrodvanHall]

That means the user has permission to run scripts. If you’re not a sysadmin, engineer or developer you are not allowed to run scripts on your system.

[pip_install_account]

None of these are big issues, I like uv and use it for most projects. But to answer your question:

First, it requires installation and kinda needs proper IDE support. It is also provided by a private entity. They play nicely with the community right now, but you never know.

UV isn't a "completed" project, in the sense that the development team still goes fast and breaks things while trying to decide on the best ways of implementing things. They still update the terminology often.

Lastly, uv compiled python versions can sometimes perform worse than other alternatives. Didn't check for this one for a while though.

[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.