Sample
Deterministically remove some optional blank lines and bracketed line breaks
| Method | Score | Scale |
|---|---|---|
| Posnett | 0.65 | 0–1; higher is more readable |
| Dorn | 0.86 | 0–1; higher is more readable |
| Mi | 0.307 | 0–1; higher is more readable |
| LLOC | 6 | Logical lines; fewer is more readable |
| DeepSeek V4 Pro | 17.67 | 0–20; mean of three runs |
| GPT-6.1 Sol | 18 | 0–20; mean of three runs |
| BTTF | 0.789 | 0–1; higher is more readable |
Loading feature diagnosis…
| Feature | Value | Contribution (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.692 | −7.039 |
| Halstead volumeHow much symbolic information the code contains. It combines the total number of operators and values with the number of distinct ones. | 157.891 | −5.21 |
| Source linesThe number of non-empty source lines. | 10 | +4 |
Intercept 8.87 + feature contributions = 0.621 (log-odds).
Score = sigmoid(0.621) = 0.65.
| Feature | Value | Contribution (log-odds) |
|---|---|---|
| Operator visual areaThe share of the code’s visual area occupied by operators such as +, =, and *. | 0.019 | +0.761 |
| Comment layout frequencyHow frequently the layout switches between lines containing only comments or whitespace and lines containing code. | 11 | +0.647 |
| 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. | 74 | +0.531 |
| 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. | 9.88 | −0.272 |
| Comment layout (horizontal)How rapidly the visual pattern of comment characters changes from left to right. | 60.636 | +0.174 |
Intercept 0.07 + feature contributions = 1.813 (log-odds).
Score = sigmoid(1.813) = 0.86.
| Score | 0.307 |
|---|
| Score | 6 |
|---|
The code is highly readable and well-structured. It uses clear imports with future annotations for modern type hinting. The exception class `ConnectTimeout` inherits logically from `ConnectionError` and `Timeout`, accurately reflecting its purpose. The docstring concisely explains when the error occurs and explicitly notes that retrying is safe, which is crucial for error handling. Nesting is nonexistent, and each import is on its own line, following clean action granularity. The code length is minimal and avoids unnecessary complexity. Reading flow is natural: imports first, then class definition with documentation. Minor deductions only because the docstring could include a period after the first sentence, and the class body contains only a docstring, which is acceptable for an exception class.
The code is highly readable. It has a clear, flat structure with no nesting and a logical organization: imports, then a single class definition. Each import is on its own line, and the class signature is concise. The docstring clearly explains the error's purpose and retry semantics, making the intent unambiguous. The code is minimal and does not contain any redundant or overly long portions. Action granularity is excellent—each line performs one distinct action—and the reading flow is natural, from imports to class definition to documentation.
This code is highly readable. It has a clear, logical structure with standard imports and a single well-defined class. Nesting is minimal—only one level for the class and its docstring, keeping the code flat. Intent is explicit: the class name and docstring clearly describe the error condition and its retry-safe implication. Code length is concise and avoids unnecessary verbosity. Action granularity is excellent; each import and class definition occupies its own line, and the docstring is well-formatted. Reading flow is natural, progressing from future imports to third-party imports, then local imports, and finally the class definition. Minor deductions are for the aliased imports, which slightly obscure original names, and the unused `BaseHTTPError` and `CompatJSONDecodeError` imports, which could confuse readers about their purpose in this snippet.
Code Structure: Imports followed by a single exception class form a simple, logical organization. Nesting: There is no deep nesting; only the class docstring is indented. Clarity of intent: The class name and docstring clearly describe a connection timeout and its retry safety, though ConnectionError and Timeout are not defined or imported in the snippet. Code length: The class is concise, but several imports are unused in the shown code. Action granularity: Each import and declaration occupies its own line, with no bundled actions. Reading flow: The top-to-bottom flow is natural, although an additional blank line before the class would improve standard Python formatting.
Code Structure: Imports followed by a focused exception class provide a logical organization. Nesting: The code is flat, with only a class body. Clarity of intent: The class name and docstring clearly explain the connection timeout and retry safety, though ConnectionError and Timeout are not defined or imported in the snippet. Code length: Very concise, but the visible imports are unused. Action granularity: Each import and declaration occupies its own line. Reading flow: Straightforward top-to-bottom flow, slightly weakened by unused imports and limited spacing between imports and the class.
Code Structure: Imports followed by a focused exception class provide clear organization, though additional blank-line spacing would improve separation. Nesting: No nested logic, making the code easy to scan. Clarity of intent: The class name and docstring clearly explain the connection timeout and retry safety; however, ConnectionError and Timeout are not defined or imported in the snippet, leaving inheritance context unclear. Code length: Very concise, although the displayed imports are unused here and add minor clutter. Action granularity: Each import and declaration occupies its own line. Reading flow: The progression from imports to declaration to documentation is natural and straightforward.