pypa/pip

Speed up build environment creation (re-usable, faster)

Open

#7,294 建立於 2019年11月4日

在 GitHub 查看
 (19 留言) (6 反應) (0 負責人)Python (8,952 star) (3,032 fork)batch import
C: PEP 517 impacthelp wantedstate: needs discussiontype: performance

描述

Currently pip always creates all build environments from scratch, requiring network access for this. This causes a significant overhead of creating isolated build environments. Can we somehow speed-up this operation?

Idea: Creating isolated build environments from cached wheels only? Do not recreate isolated build environments from scratch, but have a master copy that we just copy.

貢獻者指南

技術棧
python
領域
build systemperformance
議題類型
performance
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
4
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
3-5 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
pip internalsPython packagingbuild isolation concepts
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
35
研究方向
Investigate the current build environment creation mechanism in pip's source code (likely in pip/ internal/build env.py). The issue proposes using a cached master copy of the environment to avoid network access and reduce overhead. Review the 19 comments for additional suggestions and constraints. Determine if a simple copy of a pre built environment is feasible, considering platform specific and dependency differences. No existing PRs are linked, so this is an open design space.