Tzu-ping Chung

It would potentially prevent a faulty package from being installed. For example, say Project A 1.0 incorrectly claims itself 1.1 during `prepare_metadata_for_wheel`. Project B depends on `A!=1.0`. A dependency resolver...

I don’t think there’s a good way to add hard dependencies based on Linux distribution variants. I think this is less about patching venv, but that on most Linux distributions,...

That depends on how CentOS packages and patches things. IIRC Debian just outright removed ensurepip without noticing it’s used by venv, which (fortunately in a sense?) made the error very...

FWIW if you know the package name in advance, you can do `pip install --find-links foo ` instead.

I was responding to kpfleming’s comment, which was talking about actually installing the built wheels. If you know the project names in advance, you can pass those to pip to...

> say, if `build` could grow a provisional `--output-format=(human|json)` option, and all non-`build` output redirected to stderr as suggested, that'd probably meet users' needs. I was going to suggest something...

Yes I think setting `PIP_INSTALL_CONSTRAINTS` should work (whether that’s a proper feature is up to debate).

It’d be pretty weird for the built-in `venv` to create a tool-specific config file; I’m more inclined to think pip and/or tools using virtual environments should fix this on its...

I’d imagine build needs to gain flags (and function arguments) for passing parameters to the isolated environment.

So the problem here is that users may need to pass additional arguments when they provision an environment. The original problem here is build dependencies need to be downloaded from...