ruff UP041
labelled unknown
Analysis Nemotron 3 Super
Flags usage of socket.timeout or asyncio.TimeoutError where direct use of TimeoutError is preferred.
Fix: Replaces socket.timeout or asyncio.TimeoutError with TimeoutError in exception contexts such as raise, except, isinstance, or issubclass expressions.
8 hazards
- Rewriting 'socket.timeout' in a variable assignment like 'exc = socket.timeout' changes the type from a class to an instance if called, altering behavior.
- If 'socket' is locally scoped or shadowed, replacing 'socket.timeout' with 'TimeoutError' may refer to a different or undefined name.
- In 'except socket.timeout as e:', the rewrite removes the alias but preserves the exception type; however, if 'socket' is deleted later, the original relied on the module's attribute while the fix does not.
- The fix may remove inline comments attached to the exception name, e.g., 'raise socket.timeout # specific timeout', losing documentation.
- If 'asyncio.TimeoutError' is imported via 'from asyncio import TimeoutError as TE', the rule does not fire, but if it did fire incorrectly, rewriting to 'TimeoutError' would break due to missing import.
- In string evaluations or dynamic lookups like 'getattr(socket, "timeout")', the rule does not apply, but if mistakenly triggered, rewriting would break semantics.
- If 'socket.timeout' is used in a context outside exception handling (e.g., as a default argument), rewriting to 'TimeoutError' may not be valid if the intent was to reference the socket module's attribute.
- When 'socket' or 'asyncio' is imported under an alias (e.g., 'import socket as s'), the rule should not fire on 's.timeout', but if it did, rewriting to 'TimeoutError' would be incorrect due to unresolved name.
Programs
| id | result | title | hazard |
|---|