1. 15 Dec, 2016 3 commits
  2. 14 Dec, 2016 4 commits
  3. 13 Dec, 2016 1 commit
  4. 12 Dec, 2016 3 commits
  5. 11 Dec, 2016 4 commits
  6. 10 Dec, 2016 9 commits
  7. 08 Dec, 2016 3 commits
  8. 07 Dec, 2016 2 commits
  9. 06 Dec, 2016 1 commit
  10. 05 Dec, 2016 3 commits
  11. 04 Dec, 2016 2 commits
    • Yen Chi Hsuan's avatar
      [socks] Refine exception model for better error handling · 4bd7d9d4
      Yen Chi Hsuan authored
      1. ProxyError now inherits from socket.error instead of IOError
      
      The only functions socks.py overrides are connect and connect_ex. In
      Python 2.x and Python <= 3.2, socket functions raises socket.error. In
      newer Python versions, those functions raises OSError instead. The name
      socket.error is preserved as an alias of OSError for backward
      compability. To keep socks.py compatible with Python's standard library,
      it should raise the same exception as raw sockets.
      
      See PEP 3151 (https://www.python.org/dev/peps/pep-3151/) for more
      information about the change in Python 3.3.
      
      2. Raise EOFError instead of IOError when the socket receives less data
      than it expects
      
      There's no common convention, but both ftplib and telnetlib raises
      EOFError for similar situations. socks.py follows them.
      
      Closes #11355
      
      In #11355, only Python 2 is affected. In Python 3, both socket.error and
      IOError are alias of OSError, so AbstractHTTPHandler.do_open correctly
      catches the error and thus InfoExtractor._is_valid_url works fine.
      4bd7d9d4
    • Sergey M․'s avatar
  12. 03 Dec, 2016 1 commit
  13. 01 Dec, 2016 2 commits
  14. 30 Nov, 2016 2 commits