From 637837d1ed13daf299626cbc3c55aad7b31da7ed Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Hannes=20J=C3=A4rrendal?= Date: Tue, 11 Nov 2025 12:03:12 +0100 Subject: [PATCH] PYTHON-1354 do not set timeout to None when calling execute_async in execute_concurrent The default timeout=_NOT_SET will use the request_timeout specified in the execution_profile. This is not the same as setting the timeout to None. This will instead result in having no timeout which is not ideal. If this behaviour really is wanted, the request_timeout can be set to None in the execution_profile instead. patch by osttra-h-jarrendal; reviewed by Bret McGuire and Brad Schoening --- cassandra/concurrent.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cassandra/concurrent.py b/cassandra/concurrent.py index 0e7bf794e0..6cf4e0df57 100644 --- a/cassandra/concurrent.py +++ b/cassandra/concurrent.py @@ -143,7 +143,7 @@ def _execute(self, idx, statement, params): while self._pending_executions: p_idx, p_statement, p_params = self._pending_executions.pop(0) try: - future = self.session.execute_async(p_statement, p_params, timeout=None, execution_profile=self._execution_profile) + future = self.session.execute_async(p_statement, p_params, execution_profile=self._execution_profile) args = (future, p_idx) future.add_callbacks( callback=self._on_success, callback_args=args,