DiamondLightSource / DiamondLightSource/python-copier-template

Spike: Investigate using `uv` to manage envtire project

未關閉
#246 5 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視
devcontainer
主要語言
Jinja
星號
25
分支
10
平均合併
4 小時 4 分鐘
30 天內合併 PR
6

描述

https://github.com/DiamondLightSource/python-copier-template/issues/245 is an easy win, we would like to make further use of `uv`. Python projects have always required a slightly awkward bringing together of many tools from many vendors, one well-written tool that can manage the venv, tasks and dependencies would be very useful.

For tasks (i.e. a replacement for `tox`) there is an outstanding issue upstream: https://github.com/astral-sh/uv/issues/5903

@coretl to comment on the issues/unknowns that need to be investigated.

## Acceptance Criteria
- A reasonable set of instructions for moving to `uv` is produced

貢獻指南

開啟貢獻指南

研究方向

Start by reading linked issue 245 and the upstream uv issue 5903, then inspect the template's current environment, task, and dependency-management approach. Done means producing a reasonable, documented set of instructions for moving the project to uv and recording the relevant issues or unknowns.

由索引模型根據 Issue 內容生成。

評估

技術堆疊
python
領域
build-system, tooling
Issue 類型
功能
難度
4/5
預估耗時
3-5 天
活躍度
停滯
描述清晰度
需要釐清
新手友好度
30/100

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。