pyup is incredibly inefficient in its connection handling

[thanatos]

If you run pyup in verbose mode, you'll see something like,

DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): pypi.org:443
DEBUG:urllib3.connectionpool:https://pypi.org:443 "GET /pypi/freezegun/json HTTP/1.1" 200 10740
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): pypi.org:443
DEBUG:urllib3.connectionpool:https://pypi.org:443 "GET /pypi/jsonschema/json HTTP/1.1" 200 11591
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): pypi.org:443
DEBUG:urllib3.connectionpool:https://pypi.org:443 "GET /pypi/mock/json HTTP/1.1" 200 7499
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): pypi.org:443
DEBUG:urllib3.connectionpool:https://pypi.org:443 "GET /pypi/moto/json HTTP/1.1" 200 24418

For each package it needs to look up on an index server, pyup is opening a fresh TLS/TCP connection. These are expensive to set up for everyone involved, and it feels like pyup would probably run considerably faster if it held on to the connection.

(pyup appears to make use of requests, which makes this rather easy to accomplish: instead of calling the request.<method> methods, simply create a Session and call the methods on that.)

[rafaelpivato]

Sounds like a valid concern to me.