News for hackers. Stuff that matters.
Re:Uv's killer feature is pulling in local dependencies by greatgib on Sunday January 12, 2025 @06:37PM (#42678239)
Ridiculous post:

The author says that a normal route would be:

   - Take the proper route:

   - Create a virtual environment

   - pip install pandas

   - Activate the virtual environment

   - Run python
Basically, out of the box, when you create an virtual it is immediately activated. And you would obviously need to have it activated before doing a pip install...

In addition, in my opinion this is the thing that would sucks about UV to have different functions being tied to a single tool execution.

It is a breeze to be able to activate a venv, and be done with it, being able to run multiple times your program in one go, even with crashes, being able to install more dependencies, test it in REPL, ...

Re:Uv's killer feature is pulling in local dependencies by hamandcheese on Sunday January 12, 2025 @08:11PM (#42678896)
You can still use traditional venvs with UV though, if you want.
Re:Uv's killer feature is pulling in local dependencies by krick on Monday January 13, 2025 @12:21AM (#42680311)
Uh, but then you don't really need uv, right?
Re:Uv's killer feature is pulling in local dependencies by hamandcheese on Monday January 13, 2025 @01:32PM (#42686818)
No, but it is insanely faster than pip.
Re:Uv's killer feature is pulling in local dependencies by astronautas on Monday January 13, 2025 @03:49AM (#42681402)
Hey, I actually made a silly mistake in my post, indeed you first activate the environment and then install stuff in it. Fixed!

I disagree though it is activated immediately, or at least to me with venv I always have to activate it explicitly.