Python typing.override: Mark Method Overrides

The @override decorator documents an intentional subclass method override.

What It Does and Why It Matters

The @override decorator documents an intentional subclass method override. Static checkers can flag misspellings and missing superclass methods; the decorator itself does not enforce those relationships during execution.

Annotations guide static tools; by default they do not validate external input or change the return value at runtime.

Step-by-Step Example

Start with the complete example below. Read the inputs and predict what the final print statement will show before you run it.

from typing import override
class Formatter:
    def show(self) -> str:
        return 'default'
class UpperFormatter(Formatter):
    @override
    def show(self) -> str:
        return 'CUSTOM'
print(UpperFormatter().show())

How the Code Works

The imports make these standard-library tools available: typing.
The definition of Formatter, UpperFormatter creates reusable behavior; its body runs only when called or instantiated as appropriate.
The print calls display the results. Compare these results with the method’s documented return type and the input used.
The annotations describe intended types for editors and checkers. They are not a replacement for validating input values when the function runs.

Expected output:

CUSTOM

For the demonstrated inputs, Python displays 'CUSTOM'. This result follows from the operation described above; change one input at a time to understand which rule matters.

What to Notice

Pay attention to the accepted input types, the returned value and the boundary behavior. Predict what changes if you replace the example input with an empty, zero, negative or missing value, where that value is meaningful for this operation.

If the task uses a library function, inspect its documented exceptions and return type before reusing it inside a larger function.

Where You Would Use This

This helps maintain larger projects where functions and data shapes cross module boundaries. Check the code with a static analyzer, and still validate data received from files, users or remote APIs. Annotation constructs do not normally enforce types automatically at runtime.

Practice Exercise

Create a subclass that overrides a method from its base class.

Before running your edited example, write down the result you expect. Then test at least one valid boundary or deliberately invalid value, using appropriate exception handling where necessary.

Reference: official Python documentation for the complete API contract and version notes.

Common Beginner Mistakes

Assuming @override makes an incompatible signature valid or automatically calls super().
Overlooking the documented condition: static checkers can flag misspellings and missing superclass methods; the decorator itself does not enforce those relationships during execution.

Key Takeaways

The @override decorator documents an intentional subclass method override.
Create a subclass that overrides a method from its base class.
Annotations guide static tools; by default they do not validate external input or change the return value at runtime.