The readme for the python back end currently has uv among several dependencies when several other dependancies could be installed with uv.
in theory having all of these run from uv instead of a python installation will reduce the amount of cross platform instructions the readme will provide. it also provides a way to pin the python version similar to how we pin the npm version for the front-end but automated as part of the config.
the one thing uv might struggle to cover is the source setup-python.sh command which runs a shell script and uses a command that only works on unix shells. if this could be reworked to run with uv that would be great but it might be harder than the rest depending on what the script does.
The readme for the python back end currently has uv among several dependencies when several other dependancies could be installed with uv.
in theory having all of these run from uv instead of a python installation will reduce the amount of cross platform instructions the readme will provide. it also provides a way to pin the python version similar to how we pin the npm version for the front-end but automated as part of the config.
the one thing uv might struggle to cover is the
source setup-python.shcommand which runs a shell script and uses a command that only works on unix shells. if this could be reworked to run with uv that would be great but it might be harder than the rest depending on what the script does.