-
-
Notifications
You must be signed in to change notification settings - Fork 783
Investigate uv as venv/package manager #17935
Copy link
Copy link
Labels
audience/nvda-devPR or issue is relevant to NVDA / Add-on developersPR or issue is relevant to NVDA / Add-on developersblocked/needs-product-decisionA product decision needs to be made. Decisions about NVDA UX or supported use-cases.A product decision needs to be made. Decisions about NVDA UX or supported use-cases.needs-triage
Milestone
Metadata
Metadata
Assignees
Labels
audience/nvda-devPR or issue is relevant to NVDA / Add-on developersPR or issue is relevant to NVDA / Add-on developersblocked/needs-product-decisionA product decision needs to be made. Decisions about NVDA UX or supported use-cases.A product decision needs to be made. Decisions about NVDA UX or supported use-cases.needs-triage
Type
Fields
Give feedbackNo fields configured for Feature.
UV seems to be a new replacement for several python eco system tools, including pip and venv. It is build by the ruff authors and claims to be much faster than tools like pip. It can also be used as a replacement for these tools without too much hazard.
I think this tool can offer us many benefits, especially as part of the x64 migration strategy.
A downside is that you need to install uv stand alone, but that's a oneliner with winget. And after that, you can either use an already installed version of python or let uv automatically use the right python version.