How deeply does Software Design for Python Programmers cover name mangling?

Defines the transformation and design rationale, but does not show the mangled spelling or its runtime internals.

Name mangling

As explained in Software Design for Python Programmers

Python name mangling is the transformation of double-underscore class attribute names to include the defining class name.

Name mangling transforms a class attribute with two leading underscores by incorporating the defining class name. Use it when a class may be subclassed and an attribute should not be accessed by subclasses, helping prevent accidental name collisions. section 2.3.1

Protecting catalogue state

An initial Catalogue uses _booklist for its stored books. When subclasses are introduced, rename that attribute to __booklist to discourage subclass access; Python then mangles the name with Catalogue. The single-underscore _is_match() method remains non-public by convention. section 2.3.1

How Software Design for Python Programmers covers it

Cover of Software Design for Python Programmers

liveBook manning.com

Read Software Design for Python Programmers on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

Refactoring to RustName mangling is the compiler transformation of symbols into unique names that encode additional implementation information.
liveBook manning.com

The Quick Python Book, Fourth EditionName mangling is Python's transformation of names beginning with two underscores by prepending a class-based prefix to reduce accidental access and inheritance collisions.

Compare how 3 books explain name mangling →

Related concepts

no_mangleaddressed by · no_mangle is a Rust attribute that prevents name mangling for an item, preserving its symbol name in compiled output.
private memberused by · A private member is a program element whose direct access is restricted to its defining class, module, file, or other language-defined scope.
namespace collisionaddresses · A namespace collision occurs when distinct software entities use the same identifier within a shared naming scope, causing ambiguity or conflict.

This explainer was generated by Manning's knowledge graph from the text of Software Design for Python Programmers. The section links point to the parts of the book it draws on.