1. 30 7月, 2021 1 次提交
  2. 26 7月, 2021 1 次提交
  3. 23 7月, 2021 3 次提交
  4. 22 7月, 2021 9 次提交
  5. 08 7月, 2021 4 次提交
  6. 07 7月, 2021 6 次提交
  7. 21 6月, 2021 1 次提交
    • G
      Fix wrong usage of socket timeout · c0c4c942
      GilbertWong 提交于
      The correct usage for `socket.create_connection` is below:
      
      >> socket.create_connection(address[, timeout[, source_address]])
      >> Connect to a TCP service listening on the Internet address (a 2-tuple (host, port)), and return the socket object. This is a higher-level function than socket.connect(): if host is a non-numeric hostname, it will try to resolve it for both AF_INET and AF_INET6, and then try to connect to all possible addresses in turn until a connection succeeds. This makes it easy to write clients that are compatible to both IPv4 and IPv6.
      
      >> Passing the optional timeout parameter will set the timeout on the socket instance before attempting to connect. If no timeout is supplied, the global default timeout setting returned by getdefaulttimeout() is used.
      
      >> If supplied, source_address must be a 2-tuple (host, port) for the socket to bind to as its source address before connecting. If host or port are ‘’ or 0 respectively the OS default behavior will be used.
      
      >> Changed in version 3.2: source_address was added.
      
      Also the semantic of connect timeout and keepalive timeout are totally
      different.
      c0c4c942
  8. 16 5月, 2021 1 次提交
  9. 08 5月, 2021 1 次提交
  10. 15 4月, 2021 1 次提交
  11. 09 12月, 2020 1 次提交
  12. 23 9月, 2020 1 次提交
  13. 20 8月, 2020 2 次提交
  14. 07 8月, 2020 1 次提交
  15. 22 4月, 2020 1 次提交
  16. 02 3月, 2020 2 次提交
  17. 08 12月, 2019 2 次提交
  18. 27 10月, 2019 2 次提交