How does the Descriptor Protocol power methods (`self`), `@property`, and `@functools.cached_property` in Python—and why is `@cached_property` a Non-Data.

A strong answer

A strong candidate frames How does the Descriptor Protocol power methods (self), @property, and @functools.cached_property in Python—and why is @cached_property a Non-Data. around the exact memory layout, compiler semantics, and hardware execution model covered in [Context Managers (__enter__, __exit__) and the Descriptor Protocol]. Walk through the 3-step object.__getattribute__ algorithm, explain how functions bind self via __get__, and trace why @cached_property omits __set__ so obj.__dict__ shadows it on subsequent reads.

A microservice opens database connections and acquires distributed Redis locks inside request handlers. Whenever a downstream validation error raises an exception mid-request, the unlock line is skipped, leaving the Redis lock held until its 60-second TTL expires—and a naive file upload handler that relies on del f instead of with open(...) leaks file descriptors under PyPy or when an exception traceback holds the frame alive!

When engineers encounter this bottleneck in production, a surface-level API description rarely explains what went wrong. In real workloads, every line of code executes against concrete hardware constraints: fixed-width memory cells, CPU cache lines, kernel descriptor tables, network socket buffers, or accelerator memory buses. Without a clear mental model of Context Managers (__enter__/__exit__) and the Descriptor Protocol (__get__/__set__), debugging degrades into guesswork—tuning timeouts, adding retries, or scaling instances blindly while the underlying architectural flaw remains untouched.

In a production interview, always connect the specification rule to its concrete runtime consequence: state what lives on the stack versus the heap or static storage segment, how the compiler or operating system validates alignments, lifetimes, and error codes, and what happens under adversarial or boundary inputs (such as zero-length buffers, integer overflow, concurrent mutation, or partial I/O). Backing your explanation with a small trace of register/memory state transitions immediately separates senior systems engineers from candidates who only memorized syntax.

What the interviewer is listening for

• Mastery of core invariant: Write exception-safe Context Managers using both __enter__/__exit__ classes and try / yield / finally generators.
• Mastery of core invariant: Trace CPython's 3-step object.__getattribute__ lookup order across Data Descriptors, instance.__dict__, and Non-Data Descriptors.
• Mastery of core invariant: Implement safe descriptors using __set_name__ without sharing state across instances.
• Hardware and ABI awareness: Explaining how sizes, alignments, calling conventions, or kernel boundaries behave on real 64-bit targets rather than relying on implementation-defined assumptions.
• Defensive engineering: Naming the exact compiler flags (-Wall -Wextra -Werror), static analyzers, or runtime sanitizers (-fsanitize=address,undefined,thread) that verify correctness in CI.

Common mistakes

• Explaining only surface syntax without tracing the underlying memory addresses, ownership lifetime, or kernel/user-space state transitions.
• Assuming undefined behavior (such as signed overflow, uninitialized reads, strict-aliasing violations, or dangling pointers) will "just work" because it passed an unoptimized -O0 debug build.
• Ignoring return codes, partial reads/writes, alignment padding, or cleanup paths when an allocation or syscall fails midway through a function.