Sample
pyint-49b4c6d86903-I13
Lower every eligible synchronous for loop to a while loop
Scores
| Method | Score | Scale |
|---|---|---|
| Posnett | 0.002 | 0–1; higher is more readable |
| Dorn | 0.799 | 0–1; higher is more readable |
| Mi | 0.48 | 0–1; higher is more readable |
| LLOC | 11 | Logical lines; fewer is more readable |
| DeepSeek V4 Pro | 17 | 0–20; mean of three runs |
| GPT-6.1 Sol | 18 | 0–20; mean of three runs |
| BTTF | 0.752 | 0–1; higher is more readable |
Views
Loading feature diagnosis…
Source regions
Feature contributions
Feature contributions
| Feature | Value | Contribution (log-odds) |
|---|---|---|
| Halstead volumeHow much symbolic information the code contains. It combines the total number of operators and values with the number of distinct ones. | 408.424 | −13.478 |
| 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.62 | −6.93 |
| Source linesThe number of non-empty source lines. | 13 | +5.2 |
Intercept 8.87 + feature contributions = -6.338 (log-odds).
Score = sigmoid(-6.338) = 0.002.
Feature contributions
| Feature | Value | Contribution (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. | 55.857 | +1.299 |
| Comment layout (horizontal)How rapidly the visual pattern of comment characters changes from left to right. | 0 | −0.804 |
| Comment layout frequencyHow frequently the layout switches between lines containing only comments or whitespace and lines containing code. | 14 | +0.541 |
| Number layout frequencyHow rapidly the number of numeric values per line changes through the code. | 1 | +0.398 |
| Operator visual areaThe share of the code’s visual area occupied by operators such as +, =, and *. | 0.057 | +0.393 |
| Indentation frequencyHow rapidly indentation changes from line to line. | 13 | −0.287 |
| Identifier layout (vertical)How rapidly the visual pattern of identifier characters changes from top to bottom. | 12.912 | −0.229 |
Intercept 0.07 + feature contributions = 1.379 (log-odds).
Score = sigmoid(1.379) = 0.799.
| Score | 0.48 |
|---|
| Score | 11 |
|---|
Run 1
The code is highly readable with a clear, logical structure. Imports are grouped and ordered conventionally, the class definition is clean and properly extends AppConfig, and the single method `ready` has a clear intent of connecting a signal. Nesting is minimal, with only one level of class-method indentation. Action granularity is appropriate — one action per statement. The reading flow is natural: config metadata first, then behavior. The only minor deduction is that the imported `base`, `get_level_tags`, and `SimpleLazyObject` are unused, and the function `update_level_tags` is not defined in this snippet; these could cause ambiguity about intent. Overall, concise and well-structured code.
Run 2
The code is generally readable with a clear structure and logical organization. It follows standard Django patterns, with concise imports and a simple class definition. There is minimal nesting, and each action is on its own line, which aids readability. The intent is clear: configure a Django app and connect a signal handler. However, the name 'update_level_tags' is referenced but not defined in the snippet, which creates ambiguity for the reader. Additionally, the imported modules 'base', 'get_level_tags', and 'SimpleLazyObject' are unused, which could confuse maintainers about their relevance. The code is concise and not overly long, but the unused imports and unexplained external function slightly reduce clarity. Overall, it is easy to follow but could benefit from minor cleanup and a comment explaining the signal connection's purpose.
Run 3
The code is clean and straightforward, with a logical structure and clear intent. It imports only what is necessary (though 'base' and 'get_level_tags' appear unused from this snippet, which slightly obscures purpose). The class is flat, with only one nested method, and each action is on its own line. The reading flow is natural, following standard Django app config patterns. Minor deductions for the unused imports and lack of a docstring explaining the signal connection behavior.
Run 1
Code Structure: Imports followed by a single configuration class provide logical organization, although several imports are unused. Nesting: Minimal nesting makes the code easy to scan. Clarity of intent: The class name, attributes, and signal connection clearly indicate Django messages configuration, but update_level_tags is neither defined nor imported in the snippet, leaving its origin unclear. Code length: The implementation is concise, with only unused imports adding unnecessary length. Action granularity: Each statement performs one clear action. Reading flow: The progression from imports to configuration attributes to startup behavior is natural; an additional blank line before the class would improve conventional formatting.
Run 2
Code Structure: Imports and the app configuration class are logically organized. Nesting: Minimal, with only a class and its method. Clarity of intent: The class metadata and signal connection clearly express app initialization, but update_level_tags is not defined or imported in the snippet, and several imports are unused. Code length: Very concise, though unused imports add clutter. Action granularity: Each statement performs one action. Reading flow: Natural progression from imports to configuration to startup behavior; an extra blank line before the top-level class would improve formatting.
Run 3
Code Structure: Imports and application configuration are logically organized, though several imports are unused in this snippet. Nesting: Minimal nesting makes the code easy to scan. Clarity of intent: The class clearly configures Django's messages application and connects a settings-change handler, but update_level_tags is neither defined nor imported, leaving its origin unclear. Code length: Short and concise, with little unnecessary code beyond the unused imports. Action granularity: Each line performs one clear action. Reading flow: Natural progression from imports to configuration attributes to initialization behavior; an additional blank line before the class would improve conventional Python formatting.