indygreg / indygreg/PyOxidizer

Avoid pip install --target

Open
#194 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
6.2k
Forks
256
PR merge metrics
No merged PRs in 30d

Description

See https://github.com/pypa/pip/issues/4390 .

IMO the pip rules should create a venv , and `--root`. Ideally even they have a optional venv name argument, so that the same venv may be re-used across several rules , allowing PyOxidizer to complete pre-reqs first, effectively allowing multiple phases of requirements to workaround the many problems of pip.

It also would mean that the pip rules could do some pip prep , and then the re-use the VirtualEnv logic.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by tracing the pip rules and the existing VirtualEnv logic. Compare the current `pip install --target` approach with the proposed venv and `--root` flow, including optional venv reuse across rules and multiple requirement phases. Done means the rules can prepare and reuse a virtual environment without the problems described in pip issue 4390.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, rust
Domain
build-system, devtools
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.