summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* 3.4.03.4.0Andy McCurdy2020-01-302-2/+2
|
* better thread-safety for ConnectionPool (#1270)Andy McCurdy2020-01-305-49/+155
| | | Better thread and fork safety for ConnectionPool and BlockingConnectionPool
* Fix spelling in docstring (#1272)Damon Jablons2020-01-301-1/+1
|
* add type filter to scan functionnetocp2020-01-303-5/+29
| | | | Fixed #1220
* Slight optimization to command packing.Andy McCurdy2019-12-292-3/+5
| | | | Fixed #1255
* Add test for pipeline.transaction(value_from_callable=True)Andy McCurdy2019-12-292-1/+9
|
* Added the 'ssl_check_hostname' option.Andy McCurdy2019-12-294-2/+19
| | | | | | | | 'ssl_check_hostname' tells SSL Connections to whether to require the TCP hostname to match the hostname specified in the SSL Cert. By default 'ssl_check_hostname' is False to maintain backwards compatibility. Fixed #1196
* more accurate description of acceptable argument typesAndy McCurdy2019-12-291-2/+2
| | | | fixes #1214
* Allow setting client_name during connection construction.Peter van Dijk2019-12-294-23/+75
| | | | | | Client instances and Connection pools now accept "client_name" as an optional argument. If supplied, all connections created will be named via CLIENT SETNAME once the connection to the server is established.
* 'with' statement for PubSub (#765)Dmitry Kuragin2019-12-292-0/+15
| | | PubSub objects are now context managers.
* Testing the boolean nature of Pipeline instance should always return True.Andy McCurdy2019-12-293-3/+17
| | | | | | | | Prior to this, pipeline instances used __len__() which returns the number of queued commands on the pipeline. When there were no queued commands, the pipeline instance would evaluate to 0 or False. Fixes #994
* Added support for ACL commandsAndy McCurdy2019-12-287-20/+536
|
* Drop support for end-of-life Python 3.4Jon Dufresne2019-12-075-9/+4
| | | | | | | | | | Python 3.4 has been EOL since 2019-03-18. Removing from the test matrix helps reduce testing resources. For additional details on unsupported Python versions, see: https://devguide.python.org/devcycle/#end-of-life-branches
* Fix simple typo: recurrsion -> recursionTim Gates2019-12-071-1/+1
| | | | Closes #1252
* Compare numbers using '==' instead of 'is' (#1245)Jon Dufresne2019-11-121-5/+5
| | | | | | While numbers are frequently singletons as an optimization, it is not guaranteed by the language specification. Fixes flake8 error: F632 use ==/!= to compare str, bytes, and int literals
* Remove deprecated license_file from setup.cfg (#1244)Jon Dufresne2019-11-121-3/+0
| | | | | | | | | | Starting with wheel 0.32.0 (2018-09-29), the "license_file" option is deprecated. The wheel will continue to include LICENSE, it is now included automatically: https://wheel.readthedocs.io/en/stable/user_guide.html#including-license-files-in-the-generated-wheel-file https://wheel.readthedocs.io/en/stable/news.html
* Unify tox and Travis test matrix (#1243)Jon Dufresne2019-11-125-47/+35
| | | | | | | | | | | | | | | tox can now always be used as the test entry point and allows for contributors to easily test the full test matrix locally. Starting with setuptools v41.5.0 (27 Oct 2019) the `setup.py test` command is formally deprecated. It now emits a warning on use. Prior to this version, it use was discouraged by the setuptools developers. Now, always use tox as the one testing entry point. It handles multiple version of Python and Redis. The Travis CI configuration was reworked to use tox to install dependencies and run tests in the same manner that contributors would do locally.
* Fix TypeError by passing optional decode_responses keyword argument d… (#1239)Jakob Keller2019-11-111-2/+5
| | | | * Fix TypeError by passing optional decode_responses keyword argument down to parse_slowlog_get()
* Add equality test on Redis client and conn pool (#1240)Rajiv Bakulesh Shah2019-11-114-0/+80
| | | Add equality test on Redis client and connection pool
* Support Python 3.8 (#1241)Rajiv Bakulesh Shah2019-11-113-2/+4
|
* Fix misplaced space (#1237)Thomas Matecki2019-10-271-1/+1
| | | Sorry, I'm a pendant.
* Allow Pipeline.execute() to execute on empty command stack if it is watching ↵Brian Maissy2019-10-243-2/+20
| | | | keys
* Update README.rstAbhishek Kumar Singh2019-10-211-36/+35
| | | Fixed `README.rst's` `code-block` directive `lang` name typo.
* Support old EPEL-7 Redis. (#1227)tuxmaster50002019-10-181-0/+7
| | | Fix test suite with Redis versions pre-5.0.0
* Version 3.3.113.3.11Andy McCurdy2019-10-133-2/+6
| | | | | | check exception.args rather than exception.message. exception.message was deprecated prior to Python 2.7 and some alternative builds have removed it completely.
* Version 3.3.103.3.10Zac Bristow2019-10-103-2/+5
| | | | | | | | | 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.
* Version 3.3.93.3.9Zac Bristow2019-10-104-6/+62
| | | | | | | | | 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.
* spelling fixes (#1218)Stephen Hassard2019-10-061-4/+4
|
* version 3.3.8, fix MONITOR output to account for all types of clients3.3.8huangwei-ds52019-08-194-3/+31
| | | | | | | | | | 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
* version 3.3.7, Fixed a socket.error regression introduced in 3.3.03.3.7Andy McCurdy2019-08-133-5/+21
| | | | | | | Prior versions of 3.3.x could potentially raise a raw socket.error (or one of its subclasses) instead of a redis.exceptions.ConnectionError. Fixes #1202
* version 3.3.6, fixed a regression in 3.3.5 with pubsub timeouts3.3.6Andy McCurdy2019-08-064-1/+20
| | | | Fixes #1200
* version 3.3.5, handle socket.timeout errors correctly in Python 2.73.3.5Andy McCurdy2019-08-023-17/+12
| | | | | Fix an issue where socket.timeout errors could be handled by the wrong exception handler in Python 2.7.
* version 3.3.4, more specifically identify nonblocking read errors3.3.4Andy McCurdy2019-07-301-1/+2
| | | | | | | versions 3.3.1, 3.3.2 and 3.3.3 could potentially hide ConnectionErrors on Python 2.7. This change accurately identifies errors by both exception class and errno to determine whether a nonblocking socket can be read
* version 3.3.4, more specifically identify nonblocking read errorsAndy McCurdy2019-07-303-15/+22
| | | | | | | versions 3.3.1, 3.3.2 and 3.3.3 could potentially hide ConnectionErrors on Python 2.7. This change accurately identifies errors by both exception class and errno to determine whether a nonblocking socket can be read
* fixed some misspellings in the changes fileAndy McCurdy2019-07-301-22/+22
|
* Version 3.3.3. Accomodate Python 2.7.x versions < 2.7.9.3.3.3Andy McCurdy2019-07-303-3/+6
| | | | | | | | The SSL module includes in Python versions < 2.7.9 does not include the SSLWantReadError or SSLWantWriteError exceptions. As such we can't assume they are present just because the ssl module happens to be installed. Fixes #1197
* Make pubsub tests more resilient on laggy connectionsAndy McCurdy2019-07-301-12/+40
| | | | | | | | | | Commands sent on pubsub connections (like subscribe, psusbscribe, etc.) do not wait for the server to acknowledge a reply. This can lead to situations where commands are executed out of order. This is more noticeable on laggy connections. This fix ensures that all anticipated messages are read off the pubsub connection before proceeding to the next command
* use a multi-connection client for multiprocess testsAndy McCurdy2019-07-291-0/+12
|
* Version 3.3.2, SSL Blocking Exceptions don't use errno.EWOULDBLOCK3.3.2Andy McCurdy2019-07-293-5/+9
| | | | Ref #1197
* version 3.3.1, fixed a regression involving SSL and non-blocking sockets3.3.1Andy McCurdy2019-07-293-9/+23
| | | | Fixes #1197
* clearer language in docs3.3.0Andy McCurdy2019-07-281-3/+3
|
* update readme with health_check_interval optionAndy McCurdy2019-07-281-0/+39
|
* version 3.3.0Andy McCurdy2019-07-282-2/+2
|
* Pipelines shouldn't retry ConnectionErrors implicitlyAndy McCurdy2019-07-282-15/+29
|
* Add an Event parameter to PubSubWorkerThread and run_in_thread so (#1195)Timothy Rule2019-07-281-5/+5
| | | | The PubSubWorkerThread now uses a `threading.Event` to control its life cycle.
* PING/PONG health checksAndy McCurdy2019-07-285-28/+275
| | | | | | | | | | | | | | | | | | | | | | The `Redis` class and the `ConnectionPool` class now support the "health_check_interval=N" option. By default N=0, which turns off health checks. `N` should be an integer, and when greater than 0, ensures that a health check is performed just before command execution anytime the underlying connection has been idle for more than N seconds. A health check is a full PING/PONG round trip to the Redis server. If a health check encounters a ConnectionError or TimeoutError, the connection is disconnected and reconnected and the health check is retried exactly once. Any error during the retry is raised to the caller. Health check retries are not governed by any other options such as `retry_on_timeout`. In systems where idle times are common, these health checks are the intended way to reconnect to the Redis server without harming any user data. When this option is enabled for PubSub connections, calling `get_message()` or `listen()` will send a health check anytime a message has not been read on the PubSub connection for `health_check_interval` seconds. Users should call `get_message()` or `listen()` at least every `health_check_interval` seconds in order to keep the connection open.
* Ability to create a client that uses a single connectionAndy McCurdy2019-07-235-56/+110
| | | | | | | | | | | | | This has multiple uses: * Single connection clients will not be considered threadsafe. This means certain settings could temporarily be adjusted. For example, a context manager could temporarily modify the encoding behavior for a set of commands. * We can introduce more thorough health checks that only happen when a connection is handed out from the connection pool. * Workloads that issue many commands to Redis should be slightly faster. Prior to this change, the client must retrieve a connection from the pool for each command.
* Fix typo in README and CHANGELOG (#1133)Jani Korhonen2019-07-182-2/+2
|
* Updates README.rst with svg badge (#1182)Nikita Sobolev2019-07-171-1/+1
|
* Handle removed claimed messages without an exceptionThomas Daskalakis2019-07-173-1/+34
| | | | Fixes #1191