Skip to content
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

pip install restarts download from scratch after "ReadTimeoutError" #4822

Closed
kaisbensalah opened this issue Oct 29, 2017 · 8 comments
Closed
Labels
auto-locked Outdated issues that have been locked by automation resolution: duplicate Duplicate of an existing issue/PR

Comments

@kaisbensalah
Copy link

  • Pip version: 9.0.1
  • Python version: 2.7
  • Operating system: Linux 4.9.0-4 (Debian)

Description:

This issue really has to be taken seriously.

The next time I run pip install after encountering a "ReadTimeoutError" (due to internet connection issue), pip doesn't resume package download from where it stopped, but rather it restarts from scratch - Such behavior is not acceptable for slow connections, as it wastes time ..

What I've run:

First try

pip install PySide --user

Downloading PySide-1.2.4.tar.gz (9.3MB)
95%|███████████████████████████ | 8.8MB 8.8kB/s eta 0:0:49
..
ReadTimeoutError: HTTPSConnectionPool(host='pypi.python.org', port=443): Read timed out.

Re-tried installing

pip install PySide --user

Downloading PySide-1.2.4.tar.gz (9.3MB)
0%| | | | | | | | | | | | | | | | | | | | |

@pradyunsg
Copy link
Member

Hi @kaisbe! Thanks for filing this issue. :)

There's already #4796 for tracking this.

@pradyunsg pradyunsg added the resolution: duplicate Duplicate of an existing issue/PR label Oct 29, 2017
@kaisbensalah
Copy link
Author

Hi @pradyunsg, thanks for letting me know.

@MilkTeaD
Copy link

Very @pradyunsg : kind of duplicate.... then in the duplicate you refer to this post ... but there is NO solution proposed.
Circular reference without an in-depth solution proposel ... I suggest you reopen the issud @kaisbe

@benoit-pierre
Copy link
Member

@MilkTeaD: the reference link was automatically added by Github because the issue was mentioned. It's normal to close duplicate issues in favor of keeping only one opened to track the problem.

@pradyunsg
Copy link
Member

@MilkTeaD Hi!

It's normal to close duplicate issues in favor of keeping only one opened to track the problem.

Indeed. As a project, it's easier to redirect all users facing the same problem to subscribe to one issue and let all the discussions happen there.

@CTimmerman
Copy link

Duplicate of which issue? I've already wasted enough time trying to figure out whether pip even retries by default to dig up the issue i've recently commented on concerning this issue.
Anyway, if someone knows how to add this snippet, that would be nice: https://gist.github.com/CTimmerman/ccf884f8c8dcc284588f1811ed99be6c

@pradyunsg
Copy link
Member

@CTimmerman #4796.

@lock
Copy link

lock bot commented Jun 2, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot added the auto-locked Outdated issues that have been locked by automation label Jun 2, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jun 2, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
auto-locked Outdated issues that have been locked by automation resolution: duplicate Duplicate of an existing issue/PR
Projects
None yet
Development

No branches or pull requests

5 participants