Examples: clarify how to build executables for a workspace

[lf-]

I think that the virtualenv does have the executables for that workspace built and in PATH, if you add it to a dev shell, right? It seems to work at least. This is not super obvious based on the docs, though. I would personally not associate "virtualenv" with "a package" in and of itself, so I was quite confused about that.

Also, the docs don't seem to show how to use uv2nix with the buildPythonPackage renderer of pyproject.nix to produce a nixpkgs python package to integrate with other tooling. It would be super helpful to have that in the docs, or instructions on why not to do it.

[adisbladis]

I think that the virtualenv does have the executables for that workspace built and in PATH, if you add it to a dev shell, right? It seems to work at least. This is not super obvious based on the docs, though. I would personally not associate "virtualenv" with "a package" in and of itself, so I was quite confused about that.

This is quite standard in Python workflows.
Both with pip (pip install -e) and the default with uv.

Also, the docs don't seem to show how to use uv2nix with the buildPythonPackage renderer of pyproject.nix to produce a nixpkgs python package to integrate with other tooling. It would be super helpful to have that in the docs, or instructions on why not to do it.

This is not, and will not be supported in uv2nix because of the number of shortcomings that are in the nixpkgs Python packaging (see pyproject.nix build docs for more details).
If you absolutely need to use nixpkgs Python packaging there is an upcoming interop module.
But I will not inherit the design flaws of nixpkgs.

[adisbladis]

Update: The new getting started guide mentions how the venv is set up and that local scripts are added to $PATH via editable packages.