Sample

pyint-a09548c72375-SRC

Unmodified source class

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 Pro16.330–20; mean of three runs
GPT-6.1 Sol160–20; mean of three runs
BTTF0.4640–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 send(self, request: PreparedRequest, **kwargs: Any) -> Response: ... def get_redirect_target(self, resp: 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 resp.is_redirect: location = resp.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. location = location.encode("latin1") return to_native_string(location, "utf8") return None def should_strip_auth(self, old_url: str, new_url: str) -> bool: """Decide whether Authorization header should be removed when redirecting""" old_parsed = urlparse(old_url) new_parsed = urlparse(new_url) if old_parsed.hostname != new_parsed.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 ( old_parsed.scheme == "http" and old_parsed.port in (80, None) and new_parsed.scheme == "https" and new_parsed.port in (443, None) ): return False # Handle default port usage corresponding to scheme. changed_port = old_parsed.port != new_parsed.port changed_scheme = old_parsed.scheme != new_parsed.scheme default_port = (DEFAULT_PORTS.get(old_parsed.scheme, None), None) if ( not changed_scheme and old_parsed.port in default_port and new_parsed.port in default_port ): return False # Standard case: root URI must match return changed_port or changed_scheme def resolve_redirects( self, resp: Response, req: PreparedRequest, stream: bool = False, timeout: _t.TimeoutType = None, verify: _t.VerifyType = True, cert: _t.CertType = None, proxies: dict[str, str] | None = None, yield_requests: bool = False, **adapter_kwargs: Any, ) -> Generator[Response, None, None]: """Receives a Response. Returns a generator of Responses or Requests.""" hist: list[Response] = [] # keep track of history url = self.get_redirect_target(resp) previous_fragment = urlparse(req.url).fragment while url: prepared_request = req.copy() # Update history and keep track of redirects. resp.history = hist[:] hist.append(resp) try: resp.content # Consume socket so it can be released except (ChunkedEncodingError, ContentDecodingError, RuntimeError): resp.raw.read(decode_content=False) if len(resp.history) >= self.max_redirects: raise TooManyRedirects( f"Exceeded {self.max_redirects} redirects.", response=resp ) # Release the connection back into the pool. resp.close() # Handle redirection without scheme (see: RFC 1808 Section 4) if url.startswith("//"): parsed_rurl = urlparse(resp.url) url = ":".join([to_native_string(parsed_rurl.scheme), url]) # Normalize url case and attach previous fragment if needed (RFC 7231 7.1.2) parsed = urlparse(url) if parsed.fragment == "" and previous_fragment: parsed = parsed._replace(fragment=previous_fragment) elif parsed.fragment: previous_fragment = parsed.fragment url = parsed.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 parsed.netloc: url = urljoin(resp.url, requote_uri(url)) else: url = requote_uri(url) prepared_request.url = to_native_string(url) self.rebuild_method(prepared_request, resp) # https://github.com/psf/requests/issues/1084 if resp.status_code not in ( codes.temporary_redirect, codes.permanent_redirect, ): # https://github.com/psf/requests/issues/3490 purged_headers = ("Content-Length", "Content-Type", "Transfer-Encoding") for header in purged_headers: prepared_request.headers.pop(header, None) prepared_request.body = None headers = prepared_request.headers headers.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. cookie_jar = cast("CookieJar", prepared_request._cookies) extract_cookies_to_jar(cookie_jar, req, resp.raw) merge_cookies(cookie_jar, self.cookies) prepared_request.prepare_cookies(cookie_jar) # Rebuild auth and proxy information. proxies = self.rebuild_proxies(prepared_request, proxies) self.rebuild_auth(prepared_request, resp) # 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. rewindable = prepared_request._body_position is not None and ( "Content-Length" in headers or "Transfer-Encoding" in headers ) # Attempt to rewind consumed file-like object. if rewindable: rewind_body(prepared_request) # Override the original request. req = prepared_request if yield_requests: yield req # type: ignore[misc] # Internal use only, returns PreparedRequest else: resp = self.send( req, stream=stream, timeout=timeout, verify=verify, cert=cert, proxies=proxies, allow_redirects=False, **adapter_kwargs, ) extract_cookies_to_jar(self.cookies, prepared_request, resp.raw) # extract redirect url, if any, for the next loop url = self.get_redirect_target(resp) yield resp def rebuild_auth( self, prepared_request: PreparedRequest, response: 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. """ original_request = response.request assert _is_prepared(original_request) assert _is_prepared(prepared_request) headers = prepared_request.headers original_url = original_request.url url = prepared_request.url if "Authorization" in headers and self.should_strip_auth(original_url, url): # If we get redirected to a new host, we should strip out any # authentication headers. del headers["Authorization"] # .netrc might have more auth for us on our new host. new_auth = get_netrc_auth(url) if self.trust_env else None if new_auth is not None: prepared_request.prepare_auth(new_auth) def rebuild_proxies( self, prepared_request: PreparedRequest, proxies: 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(prepared_request) headers = prepared_request.headers scheme = urlparse(prepared_request.url).scheme new_proxies = resolve_proxies(prepared_request, proxies, self.trust_env) if "Proxy-Authorization" in headers: del headers["Proxy-Authorization"] try: username, password = get_auth_from_url(new_proxies[scheme]) except KeyError: username, password = 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 scheme.startswith("https") and username and password: headers["Proxy-Authorization"] = _basic_auth_str(username, password) return new_proxies def rebuild_method( self, prepared_request: PreparedRequest, response: Response ) -> None: """When being redirected we may want to change the method of the request based on certain specs or browser behavior. """ method = prepared_request.method # https://tools.ietf.org/html/rfc7231#section-6.4.4 if response.status_code == codes.see_other and method != "HEAD": method = "GET" # Do what the browsers do, despite standards... # First, turn 302s into GETs. if response.status_code == codes.found and method != "HEAD": method = "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 response.status_code == codes.moved and method == "POST": method = "GET" prepared_request.method = method

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.9001.476−297.049
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.413−6.62

Intercept 8.87 + feature contributions = -169.199 (log-odds).
Score = sigmoid(-169.199) = 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.872+3.978
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.515
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.952−0.272

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

Score0.616
Score135
Run 1

The code is generally well-structured and readable. It uses clear method names, sensible docstrings, and logical grouping of related operations within the `resolve_redirects` method. Comments explain non-obvious behavior, which aids understanding. However, the `resolve_redirects` method is quite long and handles many concerns sequentially, which slightly reduces readability and maintainability. Nesting is mostly flat with two levels at most, and action granularity is good—most lines perform a single clear action. The imports are extensive but organized. Minor issues include heavy use of inline comments and some complex conditional logic, but overall the code is clear, consistent, and purposeful.

Run 2

The code is generally readable and well-structured. It logically groups related methods within a mixin class and uses clear naming. Functions have descriptive docstrings and comments that explain non-obvious behavior (e.g., redirect handling, auth stripping, cookie extraction). The code is mostly flat, with nesting limited to logical conditions and loops; the main `resolve_redirects` loop is long but avoids deep indentation. Purpose is clear throughout, and actions are usually one per line, improving traceability. However, the `resolve_redirects` method is quite long and handles many responsibilities (history, cookies, auth, proxies, rewind logic), which slightly harms scanability and flow. Some sections rely on comments to clarify complex HTTP/client behavior, which is helpful but indicates inherent complexity. Overall, the code is well-organized for an experienced Python developer, with only minor concerns about method length and density.

Run 3

The code is well-structured and follows clear logical organization, with consistent separation of concerns across methods. It is mostly flat with no deep nesting except minor conditional blocks. Comments and docstrings clarify intent, especially for non-obvious HTTP redirect handling. The code is slightly verbose in places, with some duplicate comments and repetitive status-code checks, but this improves clarity. It uses one primary action per line and maintains a natural reading flow. The inheritance pattern with abstract method signatures (send as ellipsis) is idiomatic but assumes reader familiarity. Overall, the code is highly readable with only minor verbosity.

Run 1

Code Structure: The mixin organizes redirect handling into clearly named helper methods, although resolve_redirects combines many responsibilities. Nesting: Most methods are flat with straightforward conditionals; the main redirect loop adds moderate nesting through exception handling and branches. Clarity of intent: Descriptive method names, type annotations, docstrings, and comments explain protocol quirks well. Abbreviations such as req, resp, and hist, plus unresolved annotation names in the snippet, slightly reduce clarity. Code length: Most helpers are concise, but resolve_redirects is lengthy and requires tracking substantial mutable state; some comments are verbose. Action granularity: Statements generally perform one action per line, and multiline expressions remain readable. Reading flow: Redirect processing follows a logical sequence from response cleanup through URL normalization, request rebuilding, and sending. However, repeated mutations and dependencies among cookies, headers, authentication, proxies, and request history increase the mental effort needed to follow the central method.

Run 2

Code Structure: Related redirect behavior is logically grouped in a mixin, with focused helpers for authentication, proxies, and methods; resolve_redirects handles too many responsibilities. Nesting: Mostly shallow conditionals and early returns, though the redirect loop contains several nested branches. Clarity of intent: Descriptive names, annotations, docstrings, and protocol explanations clarify purpose. However, undefined annotation references (_t and CookieJar) and a generator annotation that excludes yielded requests introduce ambiguity. Code length: Most helpers are concise, but the lengthy redirect method and extensive commentary increase reading effort. Action granularity: Statements generally perform one action per line, with clear intermediate variables. Reading flow: Redirect processing follows a coherent sequence, aided by whitespace and explanatory comments, but tracking mutations across requests, responses, cookies, and history requires sustained attention.

Run 3

Code Structure: Cohesive redirect-handling mixin with well-separated authentication, proxy, and method helpers; resolve_redirects combines many responsibilities. Nesting: Mostly shallow conditionals and early returns, though the redirect loop contains several nested branches. Clarity of intent: Descriptive method names, annotations, docstrings, and protocol-specific comments explain behavior well; undefined _t and CookieJar references and the generator's mixed yield types introduce ambiguity. Code length: Generally justified by HTTP edge cases, but the lengthy redirect routine and extensive commentary slow scanning. Action granularity: Nearly every statement performs one clear action, with no compressed multi-statement lines. Reading flow: Redirect processing follows a logical sequence, supported by whitespace and explanatory comments; numerous mutable state updates and compatibility exceptions require careful tracking.