-
-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to pip output from one pip-run to another pip-run #36
Comments
jaraco
added a commit
that referenced
this issue
Nov 12, 2018
pip-run 5.2 allows setting |
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. |
jaraco
pushed a commit
that referenced
this issue
Jun 25, 2021
This change adds `nitpicky=True` (which is an equivalent of `-n`) to make Sphinx emit warnings for any references to non-existing targets. Then, it adds `-W` to make it fail whenever a single warning is seen. Finally, `--keep-going` allows Sphinx to print out all the warnings before exiting instead of showing just one and bailing. Resolves #29 Refs: * https://www.sphinx-doc.org/en/master/man/sphinx-build.html#cmdoption-sphinx-build-n * https://www.sphinx-doc.org/en/master/man/sphinx-build.html#cmdoption-sphinx-build-W * https://www.sphinx-doc.org/en/master/man/sphinx-build.html#cmdoption-sphinx-build-keep-going
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.The text was updated successfully, but these errors were encountered: