1. 10 5月, 2020 1 次提交
  2. 30 4月, 2020 1 次提交
  3. 02 2月, 2020 1 次提交
  4. 01 2月, 2020 1 次提交
    • A
      Provide AUTH fallback support for connection URLs with a username component · e39ae455
      Andy McCurdy 提交于
      Prior to ACL support, redis-py ignored the username component of
      Connection URLs. With ACL support, usernames are no longer ignored and
      are used to authenticate against an ACL rule. Some cloud vendors with
      managed Redis instances (like Heroku) provide connection URLs with a
      username component pre-ACL that is not intended to be used. Sending that
      username to Redis servers < 6.0.0 results in an error. Attempt to detect
      this condition and retry the AUTH command with only the password such
      that authentication continues to work for these users.
      
      Fixes #1274
      e39ae455
  5. 31 1月, 2020 2 次提交
  6. 13 10月, 2019 1 次提交
    • A
      Version 3.3.11 · 53772852
      Andy McCurdy 提交于
      check exception.args rather than exception.message. exception.message
      was deprecated prior to Python 2.7 and some alternative builds have
      removed it completely.
      53772852
  7. 11 10月, 2019 2 次提交
    • Z
      Version 3.3.10 · e1bc3854
      Zac Bristow 提交于
      Fix SSL regression introduced in 3.3.9
      
      The wrapper introduced to handle SSL timeout errors in Python 2.7
      incorrectly assumed that instances of SSLError would always have a
      string as their first element. The safer approach is to check the
      message attribute on the error.
      e1bc3854
    • Z
      Version 3.3.9 · a03c12e5
      Zac Bristow 提交于
      Fixes SSL read timeouts in Python 2.7
      
      The ssl module in Python 2.7 raises timeouts as ssl.SSLError instead of
      socket.timeout. When these timeouts are encountered, the error will be
      re-raised as socket.timeout so it is handled appropriately by the
      connection.
      a03c12e5
  8. 20 8月, 2019 1 次提交
    • H
      version 3.3.8, fix MONITOR output to account for all types of clients · d811ae71
      huangwei-ds5 提交于
      The client section of MONITOR output varies for TCP connections, unix socket
      connections and commands executed from Lua scripts. Account for each of these
      cases by including an additional key `client_type` in the MONITOR output.
      `client_type` will be one of ('tcp', 'unix', 'lua'). `client_address` and
      `client_port` vary based on the `client_type`.
      
      Fixes #1201
      d811ae71
  9. 14 8月, 2019 1 次提交
  10. 07 8月, 2019 1 次提交
  11. 03 8月, 2019 1 次提交
  12. 31 7月, 2019 2 次提交
  13. 30 7月, 2019 2 次提交
  14. 29 7月, 2019 1 次提交
  15. 10 7月, 2019 1 次提交
  16. 16 3月, 2019 1 次提交
  17. 18 2月, 2019 1 次提交
  18. 29 1月, 2019 1 次提交
  19. 16 11月, 2018 1 次提交
  20. 15 11月, 2018 2 次提交
  21. 17 8月, 2017 1 次提交
  22. 03 11月, 2015 2 次提交
  23. 15 8月, 2014 1 次提交
  24. 12 8月, 2014 1 次提交
  25. 03 6月, 2014 1 次提交
  26. 02 6月, 2014 1 次提交
  27. 28 5月, 2014 1 次提交
    • A
      Don't retry commands that fail due to a socket.timeout by default. · 0647659c
      Andy McCurdy 提交于
      Users now have the ability about how socket.timeout errors are handled.
      Previously socket.timeout errors were handled just like any other socket error
      in that the command would be retried once. This createed a potential race
      condition when the client sends a command to a busy Redis server that can't
      reply faster than the client's `socket_timeout` option. In this case, the server
      will still eventually process the command.
      
      There's now a `retry_on_timeout` option that's set to False by default.
      If `retry_on_timeout` is False, any socket.timeout error will raise a
      TimeoutError exception. If `retry_on_timeout` is set to True, the client
      will retry executing the command once just like other socket.error exceptions.
      
      TODO: Write better tests for this code.
      TODO: Much of this logic could/should be moved to the ConnectionPool or
            Connection objects.
      
      Fixes #261
      0647659c
  28. 13 5月, 2014 1 次提交
  29. 07 5月, 2014 1 次提交
  30. 24 1月, 2014 1 次提交
  31. 03 1月, 2014 1 次提交
  32. 24 8月, 2013 1 次提交
  33. 15 6月, 2013 1 次提交
    • A
      2.7.6 · a6302d9e
      andy 提交于
      a6302d9e
  34. 05 6月, 2013 1 次提交