This will eventually succeed, but takes a lot longer than normal because every individual package installation has lines like this:
Collecting Django
Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.VerifiedHTTPSConnection object at 0x7f68eaca8b70>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution',)': /simple/django/
Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.VerifiedHTTPSConnection object at 0x7f68eaca8898>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution',)': /simple/django/
Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.VerifiedHTTPSConnection object at 0x7f68ead04f28>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution',)': /simple/django/
Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.VerifiedHTTPSConnection object at 0x7f68ead04fd0>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution',)': /simple/django/
Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.VerifiedHTTPSConnection object at 0x7f68eaca83c8>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution',)': /simple/django/
I've tracked this down: when wagon install calls pip, it does this:
This can be reproduced like this:
This will eventually succeed, but takes a lot longer than normal because every individual package installation has lines like this:
I've tracked this down: when
wagon install
calls pip, it does this:However,
--only-binary
actually takes an argument, so it swallows the--no-index
from the command-line, meaning that pip tries to contact PyPI.(This may be related to #56, but I'm not seeing the same error output so I'm not sure.)