Sample

pyint-35072507d40f-I04

Replace names with deterministic minifier-style shortest identifiers

Matched original source

Lines672

Scores

MethodScoreScale
Posnett00–1; higher is more readable
Dorn0.0890–1; higher is more readable
Mi0.4650–1; higher is more readable
LLOC158Logical lines; fewer is more readable
DeepSeek V4 Pro3.670–20; mean of three runs
GPT-6.1 Sol100–20; mean of three runs
BTTF0.1760–1; higher is more readable

Views

Source code

from __future__ import annotations import importlib.util import os import pathlib import sys import typing as t from collections import defaultdict from functools import update_wrapper from jinja2 import BaseLoader from jinja2 import FileSystemLoader from werkzeug.exceptions import default_exceptions from werkzeug.exceptions import HTTPException from werkzeug.utils import cached_property from .. import typing as ft from ..helpers import get_root_path from ..templating import _default_template_ctx_processor class Scaffold: """Common behavior shared between :class:`~flask.Flask` and :class:`~flask.blueprints.Blueprint`. :param import_name: The import name of the module where this object is defined. Usually :attr:`__name__` should be used. :param static_folder: Path to a folder of static files to serve. If this is set, a static route will be added. :param static_url_path: URL prefix for the static route. :param template_folder: Path to a folder containing template files. for rendering. If this is set, a Jinja loader will be added. :param root_path: The path that static, template, and resource files are relative to. Typically not set, it is discovered based on the ``import_name``. .. versionadded:: 2.0 """ cli: Group name: str _static_folder: str | None = None _static_url_path: str | None = None def __init__( self, C: str, D: str | os.PathLike[str] | None = None, E: str | None = None, G: str | os.PathLike[str] | None = None, H: str | None = None, ): #: The name of the package or module that this object belongs #: to. Do not change this once it is set by the constructor. self.import_name = C self.c = D self.g = E #: The path to the templates folder, relative to #: :attr:`root_path`, to add to the template loader. ``None`` if #: templates should not be added. self.template_folder = G if H is None: H = get_root_path(self.import_name) #: Absolute path to the package on the filesystem. Used to look #: up resources contained in the package. self.root_path = H #: A dictionary mapping endpoint names to view functions. #: #: To register a view function, use the :meth:`route` decorator. #: #: This data structure is internal. It should not be modified #: directly and its format may change at any time. self.view_functions: dict[str, ft.RouteCallable] = {} #: A data structure of registered error handlers, in the format #: ``{scope: {code: {class: handler}}}``. The ``scope`` key is #: the name of a blueprint the handlers are active for, or #: ``None`` for all requests. The ``code`` key is the HTTP #: status code for ``HTTPException``, or ``None`` for #: other exceptions. The innermost dictionary maps exception #: classes to handler functions. #: #: To register an error handler, use the :meth:`errorhandler` #: decorator. #: #: This data structure is internal. It should not be modified #: directly and its format may change at any time. self.error_handler_spec: dict[ ft.AppOrBlueprintKey, dict[int | None, dict[type[Exception], ft.ErrorHandlerCallable]], ] = defaultdict(lambda: defaultdict(dict)) #: A data structure of functions to call at the beginning of #: each request, in the format ``{scope: [functions]}``. The #: ``scope`` key is the name of a blueprint the functions are #: active for, or ``None`` for all requests. #: #: To register a function, use the :meth:`before_request` #: decorator. #: #: This data structure is internal. It should not be modified #: directly and its format may change at any time. self.before_request_funcs: dict[ ft.AppOrBlueprintKey, list[ft.BeforeRequestCallable] ] = defaultdict(list) #: A data structure of functions to call at the end of each #: request, in the format ``{scope: [functions]}``. The #: ``scope`` key is the name of a blueprint the functions are #: active for, or ``None`` for all requests. #: #: To register a function, use the :meth:`after_request` #: decorator. #: #: This data structure is internal. It should not be modified #: directly and its format may change at any time. self.after_request_funcs: dict[ ft.AppOrBlueprintKey, list[ft.AfterRequestCallable[t.Any]] ] = defaultdict(list) #: A data structure of functions to call at the end of each #: request even if an exception is raised, in the format #: ``{scope: [functions]}``. The ``scope`` key is the name of a #: blueprint the functions are active for, or ``None`` for all #: requests. #: #: To register a function, use the :meth:`teardown_request` #: decorator. #: #: This data structure is internal. It should not be modified #: directly and its format may change at any time. self.teardown_request_funcs: dict[ ft.AppOrBlueprintKey, list[ft.TeardownCallable] ] = defaultdict(list) #: A data structure of functions to call to pass extra context #: values when rendering templates, in the format #: ``{scope: [functions]}``. The ``scope`` key is the name of a #: blueprint the functions are active for, or ``None`` for all #: requests. #: #: To register a function, use the :meth:`context_processor` #: decorator. #: #: This data structure is internal. It should not be modified #: directly and its format may change at any time. self.template_context_processors: dict[ ft.AppOrBlueprintKey, list[ft.TemplateContextProcessorCallable] ] = defaultdict(list, {None: [_default_template_ctx_processor]}) #: A data structure of functions to call to modify the keyword #: arguments passed to the view function, in the format #: ``{scope: [functions]}``. The ``scope`` key is the name of a #: blueprint the functions are active for, or ``None`` for all #: requests. #: #: To register a function, use the #: :meth:`url_value_preprocessor` decorator. #: #: This data structure is internal. It should not be modified #: directly and its format may change at any time. self.url_value_preprocessors: dict[ ft.AppOrBlueprintKey, list[ft.URLValuePreprocessorCallable], ] = defaultdict(list) #: A data structure of functions to call to modify the keyword #: arguments when generating URLs, in the format #: ``{scope: [functions]}``. The ``scope`` key is the name of a #: blueprint the functions are active for, or ``None`` for all #: requests. #: #: To register a function, use the :meth:`url_defaults` #: decorator. #: #: This data structure is internal. It should not be modified #: directly and its format may change at any time. self.url_default_functions: dict[ ft.AppOrBlueprintKey, list[ft.URLDefaultCallable] ] = defaultdict(list) def __repr__(self) -> str: return f"<{type(self).__name__} {self.name!r}>" def a(self, I: str) -> None: raise NotImplementedError @property def c(self) -> str | None: """The absolute path to the configured static folder. ``None`` if no static folder is set. """ if self._static_folder is not None: return os.path.join(self.root_path, self._static_folder) else: return None @static_folder.setter def c(self, J: str | os.PathLike[str] | None) -> None: if J is not None: J = os.fspath(J).rstrip(r"\/") self._static_folder = J @property def d(self) -> bool: """``True`` if :attr:`static_folder` is set. .. versionadded:: 0.5 """ return self.c is not None @property def g(self) -> str | None: """The URL prefix that the static route will be accessible from. If it was not configured during init, it is derived from :attr:`static_folder`. """ if self._static_url_path is not None: return self._static_url_path if self.c is not None: K = os.path.basename(self.c) return f"/{K}".rstrip("/") return None @static_url_path.setter def g(self, L: str | None) -> None: if L is not None: L = L.rstrip("/") self._static_url_path = L @cached_property def h(self) -> BaseLoader | None: """The Jinja loader for this object's templates. By default this is a class :class:`jinja2.loaders.FileSystemLoader` to :attr:`template_folder` if it is set. .. versionadded:: 0.5 """ if self.template_folder is not None: return FileSystemLoader(os.path.join(self.root_path, self.template_folder)) else: return None def i( self, M: str, N: str, O: dict[str, t.Any], ) -> t.Callable[[T_route], T_route]: if "methods" in O: raise TypeError("Use the 'route' decorator to use the 'methods' argument.") return self.p(N, methods=[M], **O) @setupmethod def j(self, P: str, **Q: t.Any) -> t.Callable[[T_route], T_route]: """Shortcut for :meth:`route` with ``methods=["GET"]``. .. versionadded:: 2.0 """ return self.i("GET", P, Q) @setupmethod def k(self, R: str, **S: t.Any) -> t.Callable[[T_route], T_route]: """Shortcut for :meth:`route` with ``methods=["QUERY"]``. .. versionadded:: 3.2 """ return self.i("QUERY", R, S) @setupmethod def l(self, T: str, **U: t.Any) -> t.Callable[[T_route], T_route]: """Shortcut for :meth:`route` with ``methods=["POST"]``. .. versionadded:: 2.0 """ return self.i("POST", T, U) @setupmethod def m(self, V: str, **W: t.Any) -> t.Callable[[T_route], T_route]: """Shortcut for :meth:`route` with ``methods=["PUT"]``. .. versionadded:: 2.0 """ return self.i("PUT", V, W) @setupmethod def n(self, X: str, **Y: t.Any) -> t.Callable[[T_route], T_route]: """Shortcut for :meth:`route` with ``methods=["DELETE"]``. .. versionadded:: 2.0 """ return self.i("DELETE", X, Y) @setupmethod def o(self, Z: str, **aa: t.Any) -> t.Callable[[T_route], T_route]: """Shortcut for :meth:`route` with ``methods=["PATCH"]``. .. versionadded:: 2.0 """ return self.i("PATCH", Z, aa) @setupmethod def p(self, ab: str, **ac: t.Any) -> t.Callable[[T_route], T_route]: """Decorate a view function to register it with the given URL rule and options. Calls :meth:`add_url_rule`, which has more details about the implementation. .. code-block:: python @app.route("/") def index(): return "Hello, World!" See :ref:`url-route-registrations`. The endpoint name for the route defaults to the name of the view function if the ``endpoint`` parameter isn't passed. The ``methods`` parameter defaults to ``["GET"]``. ``HEAD`` and ``OPTIONS`` are added automatically. :param rule: The URL rule string. :param options: Extra options passed to the :class:`~werkzeug.routing.Rule` object. """ def decorator(ad: T_route) -> T_route: ae = options.pop("endpoint", None) self.q(rule, ae, ad, **options) return ad return decorator @setupmethod def q( self, af: str, ag: str | None = None, ah: ft.RouteCallable | None = None, ai: bool | None = None, **aj: t.Any, ) -> None: """Register a rule for routing incoming requests and building URLs. The :meth:`route` decorator is a shortcut to call this with the ``view_func`` argument. These are equivalent: .. code-block:: python @app.route("/") def index(): ... .. code-block:: python def index(): ... app.add_url_rule("/", view_func=index) See :ref:`url-route-registrations`. The endpoint name for the route defaults to the name of the view function if the ``endpoint`` parameter isn't passed. An error will be raised if a function has already been registered for the endpoint. The ``methods`` parameter defaults to ``["GET"]``. ``HEAD`` is always added automatically, and ``OPTIONS`` is added automatically by default. ``view_func`` does not necessarily need to be passed, but if the rule should participate in routing an endpoint name must be associated with a view function at some point with the :meth:`endpoint` decorator. .. code-block:: python app.add_url_rule("/", endpoint="index") @app.endpoint("index") def index(): ... If ``view_func`` has a ``required_methods`` attribute, those methods are added to the passed and automatic methods. If it has a ``provide_automatic_methods`` attribute, it is used as the default if the parameter is not passed. :param rule: The URL rule string. :param endpoint: The endpoint name to associate with the rule and view function. Used when routing and building URLs. Defaults to ``view_func.__name__``. :param view_func: The view function to associate with the endpoint name. :param provide_automatic_options: Add the ``OPTIONS`` method and respond to ``OPTIONS`` requests automatically. :param options: Extra options passed to the :class:`~werkzeug.routing.Rule` object. """ raise NotImplementedError @setupmethod def r(self, ak: str) -> t.Callable[[F], F]: """Decorate a view function to register it for the given endpoint. Used if a rule is added without a ``view_func`` with :meth:`add_url_rule`. .. code-block:: python app.add_url_rule("/ex", endpoint="example") @app.endpoint("example") def example(): ... :param endpoint: The endpoint name to associate with the view function. """ def decorator(al: F) -> F: self.view_functions[endpoint] = al return al return decorator @setupmethod def s(self, am: T_before_request) -> T_before_request: """Register a function to run before each request. For example, this can be used to open a database connection, or to load the logged in user from the session. .. code-block:: python @app.before_request def load_user(): if "user_id" in session: g.user = db.session.get(session["user_id"]) The function will be called without any arguments. If it returns a non-``None`` value, the value is handled as if it was the return value from the view, and further request handling is stopped. This is available on both app and blueprint objects. When used on an app, this executes before every request. When used on a blueprint, this executes before every request that the blueprint handles. To register with a blueprint and execute before every request, use :meth:`.Blueprint.before_app_request`. """ self.before_request_funcs.setdefault(None, []).append(am) return am @setupmethod def u(self, an: T_after_request) -> T_after_request: """Register a function to run after each request to this object. The function is called with the response object, and must return a response object. This allows the functions to modify or replace the response before it is sent. If a function raises an exception, any remaining ``after_request`` functions will not be called. Therefore, this should not be used for actions that must execute, such as to close resources. Use :meth:`teardown_request` for that. This is available on both app and blueprint objects. When used on an app, this executes after every request. When used on a blueprint, this executes after every request that the blueprint handles. To register with a blueprint and execute after every request, use :meth:`.Blueprint.after_app_request`. """ self.after_request_funcs.setdefault(None, []).append(an) return an @setupmethod def v(self, ao: T_teardown) -> T_teardown: """Register a function to be called when the request context is popped. Typically, this happens at the end of each request, but contexts may be pushed manually during testing. .. code-block:: python with app.test_request_context(): ... When the ``with`` block exits (or ``ctx.pop()`` is called), the teardown functions are called just before the request context is made inactive. When a teardown function was called because of an unhandled exception it will be passed an error object. If an :meth:`errorhandler` is registered, it will handle the exception and the teardown will not receive it. Teardown functions must avoid raising exceptions. If they execute code that might fail they must surround that code with a ``try``/``except`` block and log any errors. The return values of teardown functions are ignored. This is available on both app and blueprint objects. When used on an app, this executes after every request. When used on a blueprint, this executes after every request that the blueprint handles. To register with a blueprint and execute after every request, use :meth:`.Blueprint.teardown_app_request`. """ self.teardown_request_funcs.setdefault(None, []).append(ao) return ao @setupmethod def w( self, ap: T_template_context_processor, ) -> T_template_context_processor: """Registers a template context processor function. These functions run before rendering a template. The keys of the returned dict are added as variables available in the template. This is available on both app and blueprint objects. When used on an app, this is called for every rendered template. When used on a blueprint, this is called for templates rendered from the blueprint's views. To register with a blueprint and affect every template, use :meth:`.Blueprint.app_context_processor`. """ self.template_context_processors[None].append(ap) return ap @setupmethod def x( self, aq: T_url_value_preprocessor, ) -> T_url_value_preprocessor: """Register a URL value preprocessor function for all view functions in the application. These functions will be called before the :meth:`before_request` functions. The function can modify the values captured from the matched url before they are passed to the view. For example, this can be used to pop a common language code value and place it in ``g`` rather than pass it to every view. The function is passed the endpoint name and values dict. The return value is ignored. This is available on both app and blueprint objects. When used on an app, this is called for every request. When used on a blueprint, this is called for requests that the blueprint handles. To register with a blueprint and affect every request, use :meth:`.Blueprint.app_url_value_preprocessor`. """ self.url_value_preprocessors[None].append(aq) return aq @setupmethod def y(self, ar: T_url_defaults) -> T_url_defaults: """Callback function for URL defaults for all view functions of the application. It's called with the endpoint and values and should update the values passed in place. This is available on both app and blueprint objects. When used on an app, this is called for every request. When used on a blueprint, this is called for requests that the blueprint handles. To register with a blueprint and affect every request, use :meth:`.Blueprint.app_url_defaults`. """ self.url_default_functions[None].append(ar) return ar @setupmethod def z( self, at: type[Exception] | int ) -> t.Callable[[T_error_handler], T_error_handler]: """Register a function to handle errors by code or exception class. A decorator that is used to register a function given an error code. Example:: @app.errorhandler(404) def page_not_found(error): return 'This page does not exist', 404 You can also register handlers for arbitrary exceptions:: @app.errorhandler(DatabaseError) def special_exception_handler(error): return 'Database connection failed', 500 This is available on both app and blueprint objects. When used on an app, this can handle errors from every request. When used on a blueprint, this can handle errors from requests that the blueprint handles. To register with a blueprint and affect every request, use :meth:`.Blueprint.app_errorhandler`. .. versionadded:: 0.7 Use :meth:`register_error_handler` instead of modifying :attr:`error_handler_spec` directly, for application wide error handlers. .. versionadded:: 0.7 One can now additionally also register custom exception types that do not necessarily have to be a subclass of the :class:`~werkzeug.exceptions.HTTPException` class. :param code_or_exception: the code as integer for the handler, or an arbitrary exception """ def decorator(au: T_error_handler) -> T_error_handler: self.A(code_or_exception, au) return au return decorator @setupmethod def A( self, av: type[Exception] | int, aw: ft.ErrorHandlerCallable, ) -> None: """Alternative error attach function to the :meth:`errorhandler` decorator that is more straightforward to use for non decorator usage. .. versionadded:: 0.7 """ ax, ay = self.B(av) self.error_handler_spec[None][ay][ax] = aw @staticmethod def B( az: type[Exception] | int, ) -> tuple[type[Exception], int | None]: """Get the exception class being handled. For HTTP status codes or ``HTTPException`` subclasses, return both the exception and status code. :param exc_class_or_code: Any exception class, or an HTTP status code as an integer. """ aA: type[Exception] if isinstance(az, int): try: aA = default_exceptions[az] except KeyError: raise ValueError( f"'{az}' is not a recognized HTTP" " error code. Use a subclass of HTTPException with" " that code instead." ) from None else: aA = az if isinstance(aA, Exception): raise TypeError( f"{aA!r} is an instance, not a class. Handlers" " can only be registered for Exception classes or HTTP" " error codes." ) if not issubclass(aA, Exception): raise ValueError( f"'{aA.__name__}' is not a subclass of Exception." " Handlers can only be registered for Exception classes" " or HTTP error codes." ) if issubclass(aA, HTTPException): return aA, aA.code else: return aA, None

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.12292.12−405.64
Source linesThe number of non-empty source lines.672+268.8
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.431−6.647

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

Feature contributions

FeatureValueContribution
(log-odds)
Comment layout frequencyHow frequently the layout switches between lines containing only comments or whitespace and lines containing code.673−22.793
Indentation frequencyHow rapidly indentation changes from line to line.305+9.812
Identifier layout (vertical)How rapidly the visual pattern of identifier characters changes from top to bottom.671.886+8.982
Operator visual areaThe share of the code’s visual area occupied by operators such as +, =, and *.0.031+0.639
Comment layout (horizontal)How rapidly the visual pattern of comment characters changes from left to right.86.321+0.588
Number layout frequencyHow rapidly the number of numeric values per line changes through the code.1+0.398
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.86.969−0.018

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

Score0.465
Score158
Run 1

The code exhibits poor readability due to extensive use of single-letter or meaningless variable names for all method parameters (e.g., C, D, E, G, H, J, L, M, N, O, etc.), which obscures intent. Method names are similarly obfuscated as sequential letters (a, c, d, g, h, i, j, k, l, m, n, o, p, q, r, s, u, v, w, x, y, z, A, B), destroying natural reading flow. While the structural organization and low nesting are acceptable, clarity of intent is severely compromised. Parameter names like 'C' for import_name and 'D' for static_folder contradict the purpose-documented comments. Action granularity is mostly one action per line, but the heavy reliance on type annotations with abbreviated types and unclear callables further harms comprehension. The long docstrings somewhat mitigate confusion, but the code itself remains ambiguous and user-hostile without extensive commentary.

Run 2

This code is extremely unreadable due to deliberate obfuscation. Identifiers are meaningless (C, D, G, H, aA, ay), method names are single letters (i, j, k, p, q, A, B), and parameters follow no semantic ordering. Core behaviors like routing and error handling are impossible to decipher without deep external knowledge. While the code is structurally flat and each line performs one action, these strengths are undermined by arbitrary naming and unclear intent. The docstrings are long but contradict the actual parameter names, creating further confusion. This appears to be a mangled version of Flask's Scaffold, where the original clarity has been intentionally destroyed.

Run 3

The code is severely obfuscated, making it nearly unreadable. Meaningful identifiers have been replaced with cryptic names (C, D, G, H, a-z as method names), destroying clarity of intent. Parameter names like C, D, E for import_name, static_folder, etc. obscure purpose. Method names such as a(), p(), q(), z() convey nothing about behavior. This creates high cognitive load and requires constant cross-referencing. The structure retains logical docstrings, but the identifier mangling undermines all readability criteria. Nesting is mostly flat, but action granularity is acceptable; however, these are overshadowed by the ambiguous naming. The code length is also inflated due to needing extensive comments to compensate for meaningless names. Reading flow is completely disrupted because the natural 'self-documenting' quality of well-chosen names is absent.

Run 1

Code Structure: The class logically groups initialization, properties, routing helpers, callback registration, and exception handling into separate methods. Nesting: Mostly shallow, with only small decorator closures and a modest try/except branch. Clarity of intent: Severely weakened by arbitrary identifiers such as c, q, aA, and constructor parameters C–H. Detailed docstrings and type annotations help, but documentation names do not match actual signatures, and references such as options, rule, endpoint, and static_folder are inconsistent with renamed identifiers. Code length: Executable methods are generally concise, but extensive repetitive documentation makes scanning the large class cumbersome. Action granularity: Most statements perform one clear operation; chained registration calls remain reasonably understandable. Reading flow: Consistent formatting and method grouping support navigation, but opaque cross-method calls and mismatched references repeatedly interrupt comprehension.

Run 2

Code Structure: Methods are logically grouped around configuration, routing, callbacks, and error handling, with consistent formatting. Nesting: Mostly shallow; decorator closures and exception validation add only modest depth. Clarity of intent: Detailed docstrings and type annotations help, but opaque names such as c, p, and aA obscure meaning. References to original names such as options, rule, endpoint, and static_folder conflict with renamed identifiers, making behavior difficult to trace. Code length: Implementations are generally concise, but extensive, repetitive documentation makes the class cumbersome to scan. Action granularity: Statements generally perform one action each, with straightforward assignments and returns; chained registration operations remain understandable. Reading flow: Consistent method patterns support navigation, but cryptic naming and documentation-to-code mismatches repeatedly interrupt comprehension.

Run 3

Code Structure: Methods are logically grouped around configuration, routing, callbacks, and error handling, with consistent formatting. Nesting: Mostly shallow; decorator closures and exception handling add only modest depth. Clarity of intent: Detailed docstrings and type annotations help, but opaque names such as c, q, and aA severely obscure meaning. References to original names, including static_folder, options, rule, and endpoint, do not match renamed definitions or parameters, making interpretation confusing. Code length: Implementations are generally concise, but extensive repetitive documentation makes the class cumbersome to scan. Action granularity: Statements usually perform one clear action, although chained registry access and mutation require some interpretation. Reading flow: Consistent method patterns and spacing support navigation, but cryptic identifiers and mismatches between documentation and implementation repeatedly interrupt comprehension.