6 posts tagged with "type-hinting"

Python is famous for being a "consenting adults" language. By default, type hints (like name: str) are just polite suggestions. If you pass an integer into a function expecting a string, Python will happily execute it-and probably crash three lines later.

In 2026, relying on "polite suggestions" isn't enough for production-grade code. To actually enforce type hinting, you have to move beyond the built-in typing module and use external guardians.

Typeguard is a lightweight yet powerful Python library that enforces type hints at runtime. Unlike static checkers (like MyPy or Pylance), which only check code before execution, Typeguard uses function decorators to ensure that function arguments and return values strictly adhere to their type annotations during execution. If a type mismatch occurs, Typeguard raises a TypeError, effectively making your type hints mandatory contracts.

This article explores various practical use cases and examples for deploying Typeguard.

Python annotations, introduced in PEP 3107 for function parameters and return values, were initially generic metadata slots. While their primary use has become type hinting (PEP 484), expert developers leverage them for advanced and niche applications that go far beyond simple type declarations.

These use cases often involve frameworks or metaprogramming to make annotations act as declarative configuration or runtime execution instructions.

The difference between "Python hints" and "typing hints" is primarily one of scope and terminology, rather than distinct technologies.

In short: Typing hints are a subset of Python hints.

This is a critical question for developers moving from dynamically-typed code to modern, type-hinted Python. The concise answer is: No, Python does not have mandatory type hints built into the language itself.

By default, the Python interpreter is dynamically typed and will ignore type hints entirely at runtime. However, you can make type hints mandatory and runtime-enforced by utilizing external tools and libraries.

This is a fundamental and often confusing concept when developers transition to using static type checking in Python: Python's type hints are advisory, not mandatory.

The core reason why passing None to a function expecting a specific type like str or int does not raise an error at runtime (on entrance) is that the Python interpreter, by default, ignores type hints.