What does typing.Self do and why does it beat TypeVar for methods?

Q: What does typing.Self do and why does it beat TypeVar for methods?

**Target Audience:** Python developers who write class hierarchies with chainable methods or alternative constructors and use a type checker. **Difficulty:** Medium **Python version:** `typing.Self` exists from Python 3.11. Runtime behaviour checked on CPython 3.11.17 and in the page runner (Pyodide 0.25.1, CPython 3.11.3). Type-checker output is from mypy 2.3.1 with `--python-version 3.11`. > **How to read this doc:** Every idea is explained in plain language first, then tagged with `📌 Interview term:` so you also learn the exact words an interviewer expects. All output shown was produced by actually running the code; the **Verified** section quotes it in full. ## 1. Why This Even Matters — A Story First A car factory has a generic "paint job" station. A sedan goes in, a painted sedan comes out; a pickup truck goes in, a painted pickup comes out. Now imagine the station stamped every car leaving it with the label "vehicle". The pickup is still a pickup, but the next station, "fit

The problem

Question presented to candidate: "I have a Shape class with chainable setters like set_scale() that return self, and a Circle subclass. If I annotate the setters -> Shape, chaining into a Circle-only method fails type checking. How does typing.Self fix that, and what did people do before it existed?"

What a strong answer should cover:

Self (PEP 673, Python 3.11, typing_extensions for older versions) means the type of the instance the method is called on, so Circle().set_scale(2) is a Circle
Annotating -> "Shape" loses the subclass; the pre-3.11 fix was a TypeVar bound to the class with self: T (and cls: type[T] for classmethods)
Self is equivalent to that bound TypeVar but needs no extra TypeVar, no annotated self, and works on attributes (next: Self | None), classmethods, __enter__ and Protocols
Returning Self obliges you to return self, cls(...) or type(self)(...): return Shape() is a type error, and runtime confirms it would give the wrong class
Limits: not allowed in static methods or module-level functions; Self in a parameter means "the same subclass", which is stricter than the base class

Code / implementation expected: Optional — a small fluent builder or alternative constructor, showing the -> Self annotation and the subclass coming back.

typing
self
python3.11

Try it yourself

Sketch your approach before you read the solution. That is what the interview tests.

Stuck? Get a hint.

A short nudge toward the approach. It will not give the answer away.

Solution

Target Audience: Python developers who write class hierarchies with chainable methods or alternative constructors and use a type checker. Difficulty: Medium Python version: typing.Self exists from Python 3.11. Runtime behaviour checked on CPython 3.11.17 and in the page runner (Pyodide 0.25.1, CPython 3.11.3). Type-checker output is from mypy 2.3.1 with --python-version 3.11.

How to read this doc: Every idea is explained in plain language first, then tagged with 📌 Interview term: so you also learn the exact words an interviewer expects. All output shown was produced by actually running the code; the Verified section quotes it in full.

1. Why This Even Matters — A Story First

A car factory has a generic "paint job" station. A sedan goes in, a painted sedan comes out; a pickup truck goes in, a painted pickup comes out. Now imagine the station stamped ever

The solution is hidden so you can try first

10 min read · 12 sections

Run the code

Edit the code and run it here. Each console line with an expected value becomes a test.

PythonFluent setters and a classmethod constructor that keep the subclass

Practice

PythonThe hard-coded-class bug, the old TypeVar spelling, Self in attributes and __enter__