Changed venv installation to use uv

[darryllam]

Thank you for developing such a convenient toolkit. When trying to install the toolkit, I was encountering some dependency issues. I used the uv dependency manager to fix my issues and I hope this can help others as well with the installation process.

[unilight]

Hi @darryllam, thanks for the PR!

I don't have muchh experience with uv, but it seems to be pretty convenient!
Just wondering -- is it possible to keep both installation methods?

Also I noticed that you put sheet under src/sheet. May I ask what is the reason for that?

[darryllam]

The reason why sheet was moved to src/sheet is because uv expects the source code to be in src in order to have the package importable in the python environment as sheet. Theoretically, it should be possible to keep both installation methods if the change in file structure does not affect the current installation method.

[eginhard]

uv should handle both a src and a flat layout, I don't think changing that is necessary.

Just wondering -- is it possible to keep both installation methods?

Everything in the pyproject.toml is Python standard, so installation with pip install . or any other package manager works as well.

[eginhard]

This should use the correct metadata from https://github.com/unilight/sheet/blob/main/setup.cfg (which can be deleted afterwards)

[darryllam]

I have left the name field as sheet as it appears that some of the scripts within the package reference sheet rather than sheet_sqa. The other changes are now reflected in the latest push

[unilight]

Hi, (again I am not familiar with uv at all, but if what @eginhard suggested is correct then) it will be super nice to (1) keep the sheet/ structure rather than changing to src/sheet (2) keep tools/venv so we don't need to update every path.sh.

[darryllam]

I believe that I have made the requested changes now. Let me know if there are any other changes that are needed!