This might be overkill but
- Each uv version can only install one patch version per python minor version
- pip does not upgrade uv by default when the run_job.sh script runs on htcondor
- So uv gets older and older over time
- If we specified the python version exactly in pyproject.toml, when we upgraded to a new patch version the htcondor workers would break because uv is old and can't install the new patch version
- Currently we let the patch version float in pyproject.toml and .python-versions due to this
If we need to specify a python patch version:
- We need to specify the uv version on the pip install line in run_job.sh since the uv version is bound to the python patch version
- That means the server needs to know the uv version
- Putting it in the run_job script means that it'd be easy to break things by changing pyproject.toml and not changing the run_job script
- Maybe add a comment in pyproject.toml and parse it in run_job.sh? Yuck
This might be overkill but
If we need to specify a python patch version: