Sample

pyint-6edef4376c0c-I03

Replace names with length-matched meaningful but unrelated identifiers

Matched original source

Lines314

Scores

MethodScoreScale
Posnett00–1; higher is more readable
Dorn0.070–1; higher is more readable
Mi0.6160–1; higher is more readable
LLOC135Logical lines; fewer is more readable
DeepSeek V4 Pro4.330–20; mean of three runs
GPT-6.1 Sol110–20; mean of three runs
BTTF0.3530–1; higher is more readable

Views

Source code

from __future__ import annotations import os import sys import time from collections import OrderedDict from collections.abc import Generator, Mapping, MutableMapping from datetime import timedelta from typing import TYPE_CHECKING, Any, cast from ._internal_utils import to_native_string from ._types import is_prepared as _is_prepared from .adapters import HTTPAdapter from .auth import _basic_auth_str from .compat import cookielib, urljoin, urlparse from .cookies import ( RequestsCookieJar, cookiejar_from_dict, extract_cookies_to_jar, merge_cookies, ) from .exceptions import ( ChunkedEncodingError, ContentDecodingError, InvalidSchema, TooManyRedirects, ) from .hooks import default_hooks, dispatch_hook from .models import ( # noqa: F401 DEFAULT_REDIRECT_LIMIT, REDIRECT_STATI, PreparedRequest, Request, Response, ) from .status_codes import codes from .structures import CaseInsensitiveDict from .utils import ( # noqa: F401 DEFAULT_PORTS, default_headers, get_auth_from_url, get_environ_proxies, get_netrc_auth, requote_uri, resolve_proxies, rewind_body, should_bypass_proxies, # re-export for external consumers to_key_val_list, ) class SessionRedirectMixin: max_redirects: int trust_env: bool cookies: RequestsCookieJar def save(self, address: PreparedRequest, **window: Any) -> Response: ... def validateMessage(self, step: Response) -> str | None: """Receives a Response. Returns a redirect URI or ``None``""" # Due to the nature of how requests processes redirects this method will # be called at least once upon the original response and at least twice # on each subsequent redirect response (if any). # If a custom mixin is used to handle this logic, it may be advantageous # to cache the redirect location onto the response object as a private # attribute. if step.is_redirect: response = step.headers["location"] # Currently the underlying http module on py3 decode headers # in latin1, but empirical evidence suggests that latin1 is very # rarely used with non-ASCII characters in HTTP headers. # It is more likely to get UTF8 header rather than latin1. # This causes incorrect handling of UTF8 encoded location headers. # To solve this, we re-encode the location in latin1. response = response.encode("latin1") return to_native_string(response, "utf8") return None def validateAddress(self, nextKey: str, balance: str) -> bool: """Decide whether Authorization header should be removed when redirecting""" localScore = urlparse(nextKey) nextClient = urlparse(balance) if localScore.hostname != nextClient.hostname: return True # Special case: allow http -> https redirect when using the standard # ports. This isn't specified by RFC 7235, but is kept to avoid # breaking backwards compatibility with older versions of requests # that allowed any redirects on the same host. if ( localScore.scheme == "http" and localScore.port in (80, None) and nextClient.scheme == "https" and nextClient.port in (443, None) ): return False # Handle default port usage corresponding to scheme. currentOrder = localScore.port != nextClient.port currentAccount = localScore.scheme != nextClient.scheme secureStatus = (DEFAULT_PORTS.get(localScore.scheme, None), None) if ( not currentAccount and localScore.port in secureStatus and nextClient.port in secureStatus ): return False # Standard case: root URI must match return currentOrder or currentAccount def validateAccount( self, mode: Response, age: PreparedRequest, config: bool = False, context: _t.TimeoutType = None, result: _t.VerifyType = True, data: _t.CertType = None, profile: dict[str, str] | None = None, defaultBalance: bool = False, **pendingAddress: Any, ) -> Generator[Response, None, None]: """Receives a Response. Returns a generator of Responses or Requests.""" size: list[Response] = [] # keep track of history key = self.validateMessage(mode) primarySession = urlparse(age.url).fragment while key: currentBalance = age.copy() # Update history and keep track of redirects. mode.history = size[:] size.append(mode) try: mode.content # Consume socket so it can be released except (ChunkedEncodingError, ContentDecodingError, RuntimeError): mode.raw.read(decode_content=False) if len(mode.history) >= self.max_redirects: raise TooManyRedirects( f"Exceeded {self.max_redirects} redirects.", response=mode ) # Release the connection back into the pool. mode.close() # Handle redirection without scheme (see: RFC 1808 Section 4) if key.startswith("//"): secureIndex = urlparse(mode.url) key = ":".join([to_native_string(secureIndex.scheme), key]) # Normalize url case and attach previous fragment if needed (RFC 7231 7.1.2) target = urlparse(key) if target.fragment == "" and primarySession: target = target._replace(fragment=primarySession) elif target.fragment: primarySession = target.fragment key = target.geturl() # Facilitate relative 'location' headers, as allowed by RFC 7231. # (e.g. '/path/to/resource' instead of 'http://domain.tld/path/to/resource') # Compliant with RFC3986, we percent encode the url. if not target.netloc: key = urljoin(mode.url, requote_uri(key)) else: key = requote_uri(key) currentBalance.url = to_native_string(key) self.validateStatus(currentBalance, mode) # https://github.com/psf/requests/issues/1084 if mode.status_code not in ( codes.temporary_redirect, codes.permanent_redirect, ): # https://github.com/psf/requests/issues/3490 currentRequest = ("Content-Length", "Content-Type", "Transfer-Encoding") for window in currentRequest: currentBalance.headers.pop(window, None) currentBalance.body = None history = currentBalance.headers history.pop("Cookie", None) # Extract any cookies sent on the response to the cookiejar # in the new request. Because we've mutated our copied prepared # request, use the old one that we haven't yet touched. activeMode = cast("CookieJar", currentBalance._cookies) extract_cookies_to_jar(activeMode, age, mode.raw) merge_cookies(activeMode, self.cookies) currentBalance.prepare_cookies(activeMode) # Rebuild auth and proxy information. profile = self.validateSession(currentBalance, profile) self.checkSession(currentBalance, mode) # A failed tell() sets `_body_position` to `object()`. This non-None # value ensures `rewindable` will be True, allowing us to raise an # UnrewindableBodyError, instead of hanging the connection. activeItem = currentBalance._body_position is not None and ( "Content-Length" in history or "Transfer-Encoding" in history ) # Attempt to rewind consumed file-like object. if activeItem: rewind_body(currentBalance) # Override the original request. age = currentBalance if defaultBalance: yield age # type: ignore[misc] # Internal use only, returns PreparedRequest else: mode = self.save( age, stream=config, timeout=context, verify=result, cert=data, proxies=profile, allow_redirects=False, **pendingAddress, ) extract_cookies_to_jar(self.cookies, currentBalance, mode.raw) # extract redirect url, if any, for the next loop key = self.validateMessage(mode) yield mode def checkSession( self, currentRequest: PreparedRequest, location: Response ) -> None: """When being redirected we may want to strip authentication from the request to avoid leaking credentials. This method intelligently removes and reapplies authentication where possible to avoid credential loss. """ primaryBalance = location.request assert _is_prepared(primaryBalance) assert _is_prepared(currentRequest) profile = currentRequest.headers secureConfig = primaryBalance.url key = currentRequest.url if "Authorization" in profile and self.validateAddress(secureConfig, key): # If we get redirected to a new host, we should strip out any # authentication headers. del profile["Authorization"] # .netrc might have more auth for us on our new host. shipment = get_netrc_auth(key) if self.trust_env else None if shipment is not None: currentRequest.prepare_auth(shipment) def validateSession( self, pendingBalance: PreparedRequest, summary: dict[str, str] | None, ) -> dict[str, str]: """This method re-evaluates the proxy configuration by considering the environment variables. If we are redirected to a URL covered by NO_PROXY, we strip the proxy configuration. Otherwise, we set missing proxy keys for this URL (in case they were stripped by a previous redirect). This method also replaces the Proxy-Authorization header where necessary. :rtype: dict """ assert _is_prepared(pendingBalance) nextKey = pendingBalance.headers buffer = urlparse(pendingBalance.url).scheme recentScore = resolve_proxies(pendingBalance, summary, self.trust_env) if "Proxy-Authorization" in nextKey: del nextKey["Proxy-Authorization"] try: customer, duration = get_auth_from_url(recentScore[buffer]) except KeyError: customer, duration = None, None # urllib3 handles proxy authorization for us in the standard adapter. # Avoid appending this to TLS tunneled requests where it may be leaked. if not buffer.startswith("https") and customer and duration: nextKey["Proxy-Authorization"] = _basic_auth_str(customer, duration) return recentScore def validateStatus( self, currentRequest: PreparedRequest, localKey: Response ) -> None: """When being redirected we may want to change the method of the request based on certain specs or browser behavior. """ result = currentRequest.method # https://tools.ietf.org/html/rfc7231#section-6.4.4 if localKey.status_code == codes.see_other and result != "HEAD": result = "GET" # Do what the browsers do, despite standards... # First, turn 302s into GETs. if localKey.status_code == codes.found and result != "HEAD": result = "GET" # Second, if a POST is responded to with a 301, turn it into a GET. # This bizarre behaviour is explained in Issue 1704. if localKey.status_code == codes.moved and result == "POST": result = "GET" currentRequest.method = result

Loading feature diagnosis…

Source regions

Feature contributions

Feature contributions

FeatureValueContribution
(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.9080.805−299.667
Source linesThe number of non-empty source lines.314+125.6
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.443−6.665

Intercept 8.87 + feature contributions = -171.861 (log-odds).
Score = sigmoid(-171.861) = 0.

Feature contributions

FeatureValueContribution
(log-odds)
Comment layout frequencyHow frequently the layout switches between lines containing only comments or whitespace and lines containing code.315−10.117
Indentation frequencyHow rapidly indentation changes from line to line.246+7.772
Number layout frequencyHow rapidly the number of numeric values per line changes through the code.246−5.224
Identifier layout (vertical)How rapidly the visual pattern of identifier characters changes from top to bottom.313.83+3.977
Comment layout (horizontal)How rapidly the visual pattern of comment characters changes from left to right.92.959+0.695
Operator visual areaThe share of the code’s visual area occupied by operators such as +, =, and *.0.044+0.512
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.92.968−0.273

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

Score0.616
Score135
Run 1

The code is severely obfuscated. Function and variable names like 'validateMessage', 'validateAddress', 'localScore', 'nextClient', 'currentBalance', 'profile', 'activeMode' are misleading and do not match their actual roles (e.g., 'validateMessage' returns a redirect URL). This obscures the code's clear purpose, which is standard HTTP redirect handling. The structure is tangled with renamed variables and functions, making it very hard to follow. Nesting is deep, especially in 'validateAccount', with multiple conditional blocks and a long while loop. Action granularity is mixed; some lines contain complex operations. The reading flow is disorganized and unnatural, resembling poorly renamed code from an obfuscator rather than maintainable software. Overall, it is barely readable due to pervasive naming and structural confusion.

Run 2

The code is highly unreadable due to intentionally obfuscated variable and method names (e.g., 'save' for send, 'validateMessage' for resolve_redirects, 'validateAccount' for resolve_redirects generator, 'size' for history, 'key' for redirect_url, 'window' for header names). This destroys clarity of intent and makes the logic nearly impossible to follow without deep familiarity. While the structure mirrors the original 'requests' library structure and nesting is moderate, the arbitrary renaming breaks the reading flow completely. The code length is acceptable and action granularity is mostly fine, but the meaningless identifiers override any structural strengths. Comments are present but refer to original concepts, disconnected from the renamed code.

Run 3

The code is difficult to read due to heavily obfuscated variable names that obscure intent (e.g., 'age', 'mode', 'currentBalance', 'localScore', 'nextClient' instead of meaningful names like 'prepared_request', 'response', 'redirect_url'). The structure is tangled across several long methods with nested conditionals and multi-line boolean logic. Action granularity is mixed: some lines perform multiple conceptual steps while others are broken into cryptic sub-expressions. The reading flow is unnatural because the logic jumps between URL parsing, header manipulation, cookie handling, and auth checks without clear section separation. While the code is syntactically valid and includes some comments, the comments do not compensate for the unclear naming and disorganized control flow. The original intent is partially recoverable due to domain comments, but overall maintainability and readability are poor.

Run 1

Code Structure: Redirect handling is divided into focused helper methods, but validateAccount combines many responsibilities in one large routine. Nesting: Mostly moderate, with a main loop and manageable conditionals rather than deeply nested branches. Clarity of intent: Docstrings, comments, and type annotations explain HTTP behavior, but misleading names such as currentBalance, shipment, duration, and validateStatus obscure requests, credentials, and method rewriting. Code length: The main redirect method is lengthy; much complexity is justified by protocol requirements, though extracting additional helpers would improve readability. Action granularity: Most lines perform one action, with no dense statement chains. Reading flow: Processing follows a logical redirect lifecycle, but generic or unrelated identifiers force readers to repeatedly consult comments and infer types. References to undefined _t and CookieJar in the supplied snippet also make annotations harder to interpret.

Run 2

1. Code Structure: Redirect handling, authentication, proxies, and method changes are separated into methods, but validateAccount combines many responsibilities. 2. Nesting: Mostly shallow conditionals and early returns; the redirect loop adds moderate nesting without becoming excessive. 3. Clarity of intent: Docstrings, protocol references, and comments explain behavior, but misleading names such as currentBalance, localScore, and validateAccount obscure HTTP concepts. Unresolved type references also distract readers. 4. Code length: Smaller helpers are reasonably concise, while the lengthy redirect method and extensive comments increase reading effort. 5. Action granularity: Generally one operation per line, with readable multiline conditions and calls. 6. Reading flow: Operations follow a logical redirect lifecycle, but inconsistent naming and numerous state mutations make tracking requests, responses, and URLs difficult.

Run 3

Code Structure: Methods separate redirect, authentication, proxy, and HTTP-method handling logically, but validateAccount combines many responsibilities. Nesting: Mostly moderate, with straightforward conditionals; the long redirect loop adds complexity without excessive depth. Clarity of intent: Docstrings, comments, and recognizable HTTP APIs explain behavior, but misleading names such as balance, shipment, duration, and validateAccount obscure domain meaning. Undefined annotation aliases such as _t also distract readers. Code length: Much of the length supports legitimate protocol edge cases, though the central method is lengthy and could be decomposed. Action granularity: Generally one operation per line, with readable multiline conditions and calls. Reading flow: Processing follows a coherent redirect lifecycle, but inconsistent naming, repeated state mutation, and numerous intermediate aliases force readers to continually reconstruct what each value represents.