[HellsMaddy]

I really love this and I've been using it a lot. The one thing I'm unsure about is the best way to get my LSP working with inline dependencies.

Usually, when I use uv along with a pyproject.toml, I'll activate the venv before starting neovim, and then my LSP (basedpyright) is aware of the dependencies and it all just works. But with inline dependencies, I'm not sure what the best way to do this is.

I usually end up just manually creating a venv with the dependencies so I can edit inside of it, but then I run the script using the shebang/inline dependencies when I'm done developing it.

[CraigJPerry]

Yeah i don't think there is a neater way to do this right now. One thing that maybe saves some effort is a "uv sync" will pay attention to the $VIRTUAL_ENV env var, but only if that var points to a venv that already exists. You can't point to an empty dir and have it create the venv.

  # make a venv somehow, probably via the editor so it knows about the venv, saving a 3rd step to tell it which venv to use
  $ env VIRTUAL_ENV=.venv/ uv sync --script foo.py

but it's still janky, not sure it saves much mental tax

[mh-]

I'd encourage using --dry-run before running uv sync, by default it can be destructive.

  By default, an exact sync is performed: uv removes packages that are not declared as dependencies of the project. Use the `--inexact` flag to keep extraneous packages.