Sample

pyint-c8fcbb975379-I12

Inline all eligible single-use intermediate local variables

Matched original source

Lines12

Scores

MethodScoreScale
Posnett0.8240–1; higher is more readable
Dorn0.9160–1; higher is more readable
Mi0.4720–1; higher is more readable
LLOC6Logical lines; fewer is more readable
DeepSeek V4 Pro15.670–20; mean of three runs
GPT-6.1 Sol170–20; mean of three runs
BTTF0.850–1; higher is more readable

Views

Source code

from __future__ import annotations from typing import TYPE_CHECKING, Any from urllib3.exceptions import HTTPError as BaseHTTPError from .compat import JSONDecodeError as CompatJSONDecodeError class Timeout(RequestException): """The request timed out. Catching this error will catch both :exc:`~requests.exceptions.ConnectTimeout` and :exc:`~requests.exceptions.ReadTimeout` errors. """

Loading feature diagnosis…

Source regions

Feature contributions

Feature contributions

FeatureValueContribution
(log-odds)
Byte entropyHow varied the bytes in the source text are. Repeated bytes give a lower value; a more even mixture gives a higher value.4.855−7.282
Halstead volumeHow much symbolic information the code contains. It combines the total number of operators and values with the number of distinct ones.146.719−4.842
Source linesThe number of non-empty source lines.12+4.8

Intercept 8.87 + feature contributions = 1.546 (log-odds).
Score = sigmoid(1.546) = 0.824.

Feature contributions

FeatureValueContribution
(log-odds)
Identifier layout (horizontal)How rapidly the visual pattern of identifier characters changes from left to right. It measures spatial frequency, not the meaning of the names.60+1.124
Operator visual areaThe share of the code’s visual area occupied by operators such as +, =, and *.0.015+0.797
Comment layout frequencyHow frequently the layout switches between lines containing only comments or whitespace and lines containing code.13+0.576
Indentation frequencyHow rapidly indentation changes from line to line.7−0.495
Number layout frequencyHow rapidly the number of numeric values per line changes through the code.1+0.398
Identifier layout (vertical)How rapidly the visual pattern of identifier characters changes from top to bottom.11.639−0.247
Comment layout (horizontal)How rapidly the visual pattern of comment characters changes from left to right.59.923+0.162

Intercept 0.07 + feature contributions = 2.385 (log-odds).
Score = sigmoid(2.385) = 0.916.

Score0.472
Score6
Run 1

The code is highly readable with a clear, logical structure. It imports only necessary components, groups them logically (standard typing, third-party, local), and defines a single, well-named exception class. Nesting is non-existent, and the class purpose is explicit through a descriptive name and a succinct docstring that explains what the error represents and how to catch it. Code length is minimal and appropriate, with one action per line where applicable. Reading flow is natural: imports, then class definition, then documentation. Minor points deducted only because the class body is entirely documentation with no custom logic, which might initially confuse some readers about its necessity, though this is common for exception classes. Overall, it adheres well to clean-code principles.

Run 2

The code is highly readable for a small fragment: it has clear intent (defining a Timeout exception), flat structure, concise length, one action per line, and natural reading flow. The docstring is informative and helpful. However, the score is limited because the code relies on external context: 'RequestException' and imported items are not defined within the snippet, making the full logical organization ambiguous. The mix of unused imports (TYPE_CHECKING, Any, BaseHTTPError, CompatJSONDecodeError) also slightly reduces clarity. Overall, it is clean but incomplete.

Run 3

The code is generally readable with clear intent and good structure. It properly imports necessary components, defines a custom exception class with a clear docstring, and maintains flat nesting. The docstring effectively communicates purpose and usage. However, the unused imports (TYPE_CHECKING, Any, BaseHTTPError, CompatJSONDecodeError) reduce clarity by suggesting incomplete implementation or missing context. The class body is minimal but includes only a docstring, which is appropriate for an exception subclass. Action granularity and reading flow are good, as each import and class definition occupies its own logical line. Overall, the code is well-organized and easy to follow, though the orphaned imports slightly detract from intentional clarity.

Run 1

Code Structure: Imports followed by a single exception class provide clear organization, though RequestException is not defined or imported in the snippet. Nesting: Minimal, with only the class body. Clarity of intent: The Timeout name and descriptive docstring clearly communicate its purpose and related exceptions. Code length: Concise, although several imports are unused in this excerpt. Action granularity: Each import and class declaration occupies its own line without combining actions. Reading flow: Natural top-to-bottom flow, with minor distractions from unused imports and insufficient blank-line separation before the class.

Run 2

Code Structure: Imports followed by a single exception class provide straightforward organization, though RequestException is not defined or imported in the snippet. Nesting: Minimal, with only a class-level docstring. Clarity of intent: The class name and docstring clearly identify a timeout exception and explain its relationship to connection and read timeouts. Code length: Concise, although several imports appear unused in this excerpt. Action granularity: Each import and declaration occupies its own line, with no compressed operations. Reading flow: Natural top-to-bottom progression; an additional blank line before the class would improve conventional formatting.

Run 3

Code Structure: Imports precede a clearly defined exception class, although the superclass RequestException is not defined or imported in the snippet. Nesting: Minimal nesting makes the code easy to scan. Clarity of intent: The Timeout name and descriptive docstring clearly explain its purpose and which errors it covers. Code length: Concise overall, though several imports appear unused within this snippet. Action granularity: Each import and declaration occupies its own line, with no compressed operations. Reading flow: Natural top-to-bottom organization; an additional blank line before the top-level class would improve conventional formatting.