Source code
from __future__ import annotations
import collections.abc as c
import hashlib
import typing as t
from collections.abc import MutableMapping
from datetime import datetime
from datetime import timezone
from itsdangerous import BadSignature
from itsdangerous import URLSafeTimedSerializer
from werkzeug.datastructures import CallbackDict
from .json.tag import TaggedJSONSerializer
class NullSession(SecureCookieSession):
"""Class used to generate nicer error messages if sessions are not
available. Will still allow read-only access to the empty session
but fail on setting.
"""
def fai(self, *arg: t.Any, **kwa: t.Any) -> t.NoReturn:
raise RuntimeError(
"The session is unavailable because no secret "
"key was set. Set the secret_key on the "
"application to something unique and secret."
)
__setitem__ = __delitem__ = clear = pop = popitem = update = setdefault = _fail
del _fail
Run 1
The code is difficult to read due to several critical issues. The method named 'fai' lacks an 'l', so it should likely be 'fail', while the alias assignment at the bottom references '_fail', which does not exist, causing a NameError at class definition time. This inconsistency severely harms clarity. The imports are scattered and contain unused or redundant aliases (e.g., collections.abc imported twice in different styles). The class overall is short, which helps length and nesting (flat structure), but the action granularity is poor: the __setitem__ assignment line crams many operations into one logical action, obscuring intent. Reading flow is broken by the naming mismatch and the misplaced 'del _fail' appearing after class-level assignments. The intent of NullSession is documented, but the implementation fails to match its own documentation and aliases, making it untrustworthy and hard to follow.
Run 2
The code has clear intent (a session class that fails on modification) and logical structure, but suffers from a critical bug: the method is defined as 'fai' but referenced as '_fail', and the reference is deleted afterward with 'del _fail'. This breaks readability and correctness. Nesting is flat and action granularity is generally fine, but the mutation of dunder methods through assignment is terse and may confuse readers unfamiliar with this pattern. The import block is slightly cluttered with unused or redundant imports (e.g., both 'collections.abc as c' and 'from collections.abc import MutableMapping'). Overall, the code is concise but ambiguous due to naming inconsistency and unconventional method assignment, lowering clarity and reading flow.
Run 3
The code is generally readable with clear intent and good structure. The class name and docstring clearly explain the purpose. Using a helper method to raise a consistent error is clean. However, the method name 'fai' appears to be a typo for 'fail', and the final line references '_fail' inconsistently, which introduces confusion. Assigning multiple dunder methods on one line reduces granularity and harms readability. Overall the code is concise and reasonably organized, but these naming inconsistencies and the condensed method assignments prevent a higher score.
Run 1
Code Structure: Imports and the session class are logically separated, but numerous unused imports add clutter, and SecureCookieSession is not defined or imported in the snippet. Nesting: Minimal nesting makes the code easy to scan. Clarity of intent: The docstring and RuntimeError clearly explain read-only behavior when a secret key is missing. However, the method is named fai while the assignments and deletion reference _fail, creating a confusing inconsistency that prevents the class from being defined as shown. Code length: The class is concise, though its import block is disproportionate to the implementation. Action granularity: Most lines perform one action, but the long chained assignment binds seven methods at once and requires more attention. Reading flow: The progression from documentation to failure handler to method bindings is natural, but the naming mismatch and unexplained base class disrupt understanding.
Run 2
Code Structure: Imports and a small class are logically organized, but numerous unused imports add clutter, and SecureCookieSession is not defined or imported in the snippet. Nesting: Minimal nesting makes the code easy to scan. Clarity of intent: The docstring and error message clearly explain read-only session behavior, but the method is named fai while assignments and deletion reference _fail, creating a confusing inconsistency. Code length: The implementation is concise, though the import list is disproportionate to its functionality. Action granularity: Most lines perform one action, but the chained assignment binds seven methods at once, reducing immediate readability. Reading flow: The progression from documentation to error handling to method bindings is natural, but the naming mismatch and undefined references interrupt comprehension.
Run 3
Code Structure: The class is logically organized, but numerous unused imports add clutter, and SecureCookieSession is not defined or imported in the snippet. Nesting: Minimal nesting makes the code easy to scan. Clarity of intent: The docstring and error message clearly explain the read-only fallback behavior, but the method name 'fai' is unclear and conflicts with the undefined '_fail' used below. Code length: The implementation is concise, although the imports are excessive for the shown code. Action granularity: Most lines perform one action, but the chained assignment binds seven methods at once, reducing readability. Reading flow: The progression from documentation to error handling to method overrides is natural, but the naming mismatch and deletion of undefined '_fail' interrupt comprehension.