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.