It's why I like using Bottle for small Python frontends: download the file and import.
(I'm ranting based on personal experiences with IT in the past. Yes in general virtualenv is the baseline)
If you're not using dependencies, and are writing 3.x code, there's very little justification.
If we use uv from TFA, like the commands are nearly 1:1:
npm install <=> uv sync
npm install foo <=> uv add foo
> It doesn't have to also store a local copy of NodeJS… which Node devs do have a thing for, too, called nvm, written in bash.
This point is true; the ecosystem simply can't change overnight. uv is getting there, I hope.
> it always works the same everywhere
`uv` works the same, everywhere?
> it actually writes down the deps
`uv add` does that, too.
> I don't have to manually switch between them (or set up fancy bashrc triggers) like venvs.
You don't have to do that with `uv`, either?
Those browser JS libs installed via <script> tags though, honestly were pretty convenient in a way.