Support for the uv package manager (uv.lock)
還沒有人認領這個 Issue。
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 52/100
- Issue 類型
- 功能
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- python
- 領域
- build-system
研究方向
先追蹤現有的 Pipfile/Pipfile.lock 支援及其產生 requirements.txt 的流程，然後將該路徑與 uv export 和通常的 pip install 路徑進行比較。當包含 uv.lock 和 pyproject.toml 的專案無需手動維護的 requirements.txt 即可推送，且涵蓋所述的 Python 版本與安裝程式 fallback 時，即視為完成。
由索引模型根據 Issue 內容生成。
描述
Hi,
I couldn't find any existing or past issues mentioning this.
It'd be great to support uv for dependency management. It's one of the most widely used Python package managers, and a lot of projects now standardise on uv.lock the way they used to on Pipfile.lock. A good number of our projects at SAP have moved over to uv + uv.lock entirely, and today those apps can't be pushed as-is -- you end up keeping a separate requirements.txt in the repo by hand, purely for compatibility with the CF Python buildpack, which rather defeats the point of having a lockfile.
The nice part is the buildpack already has the right shape for this. pipenv support works by generating a requirements.txt (from Pipfile.lock) and then handing off to the normal pip install path -- uv fits that exact pattern, and uv export exists for precisely this purpose.
Rough idea I'm thinking of would be:
- Detect
uv.lock(+pyproject.toml), much likePipfileis detected today - Run
uv export --format requirements-txtto turn the lock into arequirements.txt - Install it with
uv pip install(uv's installer is dramatically faster than pip), falling back to pip - Read the Python version from
.python-version/requires-pythoninpyproject.toml
Routing through a generated requirements.txt keeps all the existing machinery working unchanged, so it should be a reasonably contained change. plus uv ships as a PyPI wheel, so it can be added as a manifest dependency the same way pipenv is.
I'd be happy to put together a PR if this seems worth including.
Thanks!
- 主要語言
- Go
- 星號
- 122
- 分支
- 281
- PR 合併指標
- 30 天內沒有已合併 PR
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
cloudfoundry/python-buildpack 的其他 Issue
-
難度 3/5 1-2 天 新手友好度 35/100
cloudfoundry/python-buildpack#989 · 4 則留言 ·
-
Dependency Deprecation Alert可能已有人在做 @brayanhenao 於 1192 天前認領。 未關閉dependency-deprecation
cloudfoundry/python-buildpack#784 · 36 則留言 · 已指派 1 人 ·
查看 cloudfoundry/python-buildpack 的全部 Issue
相似的 Issue
-
cvss-severity:high devguard l3montree-cybersecurity/devguard/devguard pkg:golang/github.com/l3montree-dev/devguard risk:low state:open
難度 2/5 1-3 小時 新手友好度 65/100
l3montree-dev/devguard#3146 · 1 則留言 ·
維護者通常 1 天內回覆
-
CLI
難度 2/5 1-3 小時 新手友好度 82/100
databricks/cli#6910 ·
維護者通常 1 天內回覆
-
Table presenter appends a spurious ", ..." to the FIX column when all fix versions are already shown未關閉
難度 2/5 1-3 小時 新手友好度 88/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 72/100
canonical/microceph#900 · 1 則留言 ·
維護者通常 1 天內回覆
-
vulncheck or vulndb
難度 2/5 1-3 小時 新手友好度 84/100
維護者通常 1 天內回覆