8.2 Implicit Type Conversion

flowchart LR subgraph Implicit["Implicit Conversion — Python does it automatically"] I1["int: 1"] --> IR["1 + 2.5 -> 3.5 (float)"] I2["float: 2.5"] --> IR end subgraph Explicit["Explicit Conversion (Casting) — you request it directly"] E1["str: \"42\""] --> E2["int(...)"] --> E3["int: 42"] end

Implicit conversion happens automatically; explicit conversion is requested directly.

Definition

What Is It?

Python automatically converting one type to another in certain mixed-type expressions, without being asked.

Why Is It Used?

For conversions that are always safe and lossless, requiring the programmer to convert manually every time would just be repetitive noise.

Automatic Conversion Rules

The main rule: when int and float are mixed in an arithmetic expression, the int is automatically promoted to float, since float can represent every int value (within precision limits) but not vice versa.

Examples

>>> 1 + 2.5            # int automatically promoted to float
3.5
>>> type(1 + 2.5)
<class 'float'>
>>> True + 1            # bool is a subclass of int -- promotes to int
2

Advantages

No boilerplate conversion code needed for safe, common cases
Prevents accidental precision loss (never silently truncates int from a float)

Limitations

Only works for a small set of built-in, well-defined promotions (mainly numeric)
Does not apply between fundamentally incompatible types (str and int do not implicitly combine)

>>> "5" + 3       # NOT automatic -- str and int don't implicitly combine
Traceback (most recent call last):
TypeError: can only concatenate str (not "int") to str

Quick Interview Answer

“Implicit conversion is Python automatically promoting one type to another in a mixed-type expression, without an explicit call — the main real-world case is int promoting to float in mixed arithmetic, since float can safely represent every int value. It’s deliberately narrow: it only covers well-defined, lossless numeric promotions (including bool, since it’s a subclass of int), and it never bridges fundamentally incompatible types like str and int — \"5\" + 3 raises a TypeError rather than silently converting either side.”

Common Mistakes

Expecting "5" + 3 to work the way some other dynamically typed languages implicitly coerce strings and numbers — Python raises a TypeError instead.
Assuming implicit conversion happens for any “compatible-looking” types — it’s limited to the specific numeric promotions Python defines, not a general rule.