return in finally can swallow exceptions

[iritkatriel]

In three places in your codebase, you have a return statement in a finally block, which would swallow any in-flight exception:

billiard/billiard/connection.py

Line 349 in 366ac5f

return f

billiard/billiard/connection.py

Line 351 in 366ac5f

return self._get_more_data(ov, maxsize)

billiard/billiard/pool.py

Line 1856 in 366ac5f

return self._send_ack(

This means that if a BaseException (such as KeyboardInterrupt) is raised from the try body, or any exception is raised from an except: clause, it will not propagate on as expected.

See also https://docs.python.org/3/tutorial/errors.html#defining-clean-up-actions.

[auvipy]

thanks for the report! it is a very old code base, we will try to clean it asap

[imakecodes]

I upgraded my app to use the new Python 3.14 and I see the following messages in the terminal when start my Django app in dev mode:

/.venv/lib/python3.14/site-packages/billiard/pool.py:1856: SyntaxWarning: 'return' in a 'finally' block
return self._send_ack(
/.venv/lib/python3.14/site-packages/billiard/connection.py:349: SyntaxWarning: 'return' in a 'finally' block
return f
/.venv/lib/python3.14/site-packages/billiard/connection.py:351: SyntaxWarning: 'return' in a 'finally' block
return self._get_more_data(ov, maxsize)