Sample

pyint-0d5b85a73f12-I04

Replace names with deterministic minifier-style shortest identifiers

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 Pro17.330–20; mean of three runs
GPT-6.1 Sol17.330–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 exceptionally readable. It has a clear, logical structure with proper imports and a well-documented class. Nesting is non-existent, as the code is flat and straightforward. The intent is unambiguous: defining a specific exception type with a clear docstring that explains its purpose and usage. The code is concise, containing only essential elements without redundancy. Each line serves a single, clear purpose, maintaining excellent action granularity. The reading flow is natural, starting with imports, followed by the class definition and its documentation. The only minor deduction is the unused import (TYPE_CHECKING and Any), but this is negligible and doesn't significantly impact readability.

Run 3

The code is well-structured and readable. It uses clear imports, a proper class definition with a descriptive docstring, and follows standard Python conventions. The class inherits from RequestException, which is clear in intent, and the docstring concisely explains the relationship between Timeout and its subclasses. There's minimal nesting and the code is concise. Minor deductions: the unused imports (TYPE_CHECKING, Any, BaseHTTPError, CompatJSONDecodeError) slightly reduce clarity, and the class body is unusually sparse—consisting only of a docstring—which may be intentional but makes it feel like an abstract placeholder. Overall, excellent readability with only minor stylistic concerns.

Run 1

Code Structure: Imports followed by a single exception class provide a logical organization, though 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 explanatory docstring clearly communicate its purpose and relationship to connection and read timeouts. Code length: Concise overall, but several imports appear unused in this snippet. 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 top-level class would improve conventional Python formatting.

Run 2

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

Run 3

Code Structure: Imports followed by a focused exception class provide logical organization, though RequestException is not defined or imported in the snippet. Nesting: Minimal, with only a class and its docstring. Clarity of intent: The Timeout name and docstring clearly explain its purpose and related exceptions. Code length: Concise, but several imports appear unused in this excerpt. Action granularity: Each import and declaration occupies its own line, avoiding compressed operations. Reading flow: Straightforward top-to-bottom progression, although an additional blank line before the class would improve conventional formatting.