-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
build killed as a result of https://github.com/pypa/pip/issues/9284 #7752
Comments
This looks like the problem with 20.3.2: pypa/pip#9284 |
I've logged pypa/pip#9287 to report this on the pip side: pypa/pip#9287 |
Hi, we install the latest version of pip by default, you can set the version of pip to be installed using a config file https://docs.readthedocs.io/en/stable/config-file/v2.html#python version: 2
python:
version: 3.7
install:
- requirements: docs/pip.txt
- requirements: docs/requirements.txt Where pip.txt has |
Looks like a new release will be out soon pypa/pip#8936 (comment) |
This reverts commit 67ba964.
Details
Expected Result
Build as it did 4 days ago, no config changes on the project side:
https://readthedocs.org/projects/testfixtures/builds/12537398/
Actual Result
Looks like the build is now trying to download every version of every library in my project's dependencies.
I think i've found the reason:
Not sure why pip is upgrading itself to a version it knows is bad, is there anything that can fix this on the RTD side?
The text was updated successfully, but these errors were encountered: