Closed jaraco closed 6 years ago
pip-run 5.2 allows setting PIP_RUN_NO_PATCH_PREFIX
to bypass this behavior for environments that are unaffected.
Even better, pip-run 5.3 auto-detects the condition that will fail and applies the workaround there. This way, no environment variable is needed.
Consider the use-case where you want to test the encoding/decoding of some string against two versions of a library. You could do two invocations of pip-run:
And that works fine, but anyone who has spent more than 30 seconds in Unix would expect to be able to take the output of the first command and pipe it into the second command to avoid having to emit and then re-enter the intermediate result. However, if you do this with pip-run, it fails with a BrokenPipeError:
This all would work except for the (undocumented) caveat that pip-run relies on ~/.pydistutils.cfg to inject certain functionality... and so two invocations of pip-run cannot run simultaneously for the same user.
Here is the code that invokes this behavior, which implicates #14 and pypa/pip#4106.
This issue only affects invocations where the
pip install
commands frompip-run
overlap.