News for hackers. Stuff that matters.
Re:Uv is the best thing to happen to the Python ecosystem in... by jrvarela56 on Thursday October 30, 2025 @03:12AM (#45757208)
I have a directory called workspace where there’s a projects directory and the main area is for messing around. Just setup workspace once as a project.
Re:Uv is the best thing to happen to the Python ecosystem in... by BrenBarn on Thursday October 30, 2025 @03:33AM (#45757328)
But I don't want the sandbox linked in any way to a directory. I just want to be able to use it from anywhere. (This is what I can do with conda.)
Re:Uv is the best thing to happen to the Python ecosystem in... by csnweb on Thursday October 30, 2025 @04:36AM (#45757660)
You can activate the uv venv from anywhere just fine, just do source path_to_sandbox/.venv/bin/activate. Probably makes sense to define a shortcut for that like activate sandbox. Your conda env is also linked to a directory, it’s just a hidden one, you can also create the uv obe somewhere hidden. But I get it to some extent conda has this large prefilled envs with a lot of stuff in it already that work together. Still if you then end up needing anything else you wait ages for the install. I find conda so unbearable by now that I voluntarily switch every conda thing I have left over to uv the second I need to touch the conda env.
Re:Uv is the best thing to happen to the Python ecosystem in... by zelphirkalt on Thursday October 30, 2025 @05:17AM (#45757909)
A shell alias that activates workspace/sandbox?