Dive Into Python 3 (Books for Professionals by Professionals) (Mark Pilgrim)（Z-Library）

# Dive Into Python 3 — Reading Guide ## 【One-Line Pitch】 A hands-on, code-dissection approach to Python 3 for programmers who already know another language—learn by reading real, working examples that are pulled apart line-by-line and explained like a biology lesson on frog anatomy. Best for self-taught developers who prefer "show me the code" over abstract theory. ## 【Book Arc】 - **Opening (~0%–9%)**: Installation and setup across platforms, plus a "what's new in Python 3" chapter for veterans of the original Python 2 book. Covers IDLE, alternative editors/IDEs, and the philosophical shift from Python 2 to 3. - **Early (~9%–25%)**: Core data types—lists, tuples, sets, dictionaries, and None—each demonstrated through interactive shell examples. Introduces the `import` search path, docstrings, and the first real program (`approximate_size()`). - **Early-to-Middle (~25%–38%)**: Deep dive into strings, bytes, and encodings (UTF-8, CP-1252, GB18030, Big5), followed by a substantial treatment of regular expressions—from basic patterns to verbose mode with commented, readable regex. - **Middle (~38%–47%)**: Building a pluralization engine as a running case study, progressing from naive if-statements to rule-based abstraction, then to a file-driven iterator with caching. Introduces generators and the `StopIteration` protocol. - **Late (~47%+)**: Testing and debugging—assertions, unit testing philosophy, and the `itertools` module. The alphametics puzzle solver demonstrates constraint-checking with asserts and grouping with `itertools.groupby()`. ## 【Key Takeaways】 - **Python 3 is a deliberate break from Python 2** (Opening): The book targets readers who know Python 2 and want to migrate—expect emphasis on what changed, not just what's new. If you're a complete beginner, you may need supplementary material. - **Docstrings are runtime-accessible documentation** (Early): A function's docstring becomes an attribute available at runtime, and IDEs use it for tooltips. Always write them—they're not just comments, they're part of the API. - **Lists vs. tuples: mutable vs. frozen** (Early): `append()` adds one item (any type), `extend()` adds each element of a list. Tuples are "frozen lists"—convert with `tuple()` and `list()`. A one-item tuple needs a trailing comma: `(False,)` is a tuple, `(False)` is just a bool. - **Sets are for membership and set math** (Early): `in` tests membership; `union()`, `intersection()`, `difference()`, and `symmetric_difference()` cover set operations. Three of these methods are symmetric—know which ones. - **Strings vs. bytes is a real distinction** (Early): A string has characters; a bytes object has bytes. The same string encodes to different byte sequences in UTF-8, GB18030, or Big5—and decodes back correctly. This is essential for international text handling. - **Verbose regex is self-documenting** (Early): With `re.VERBOSE`, whitespace and comments are ignored, letting you write patterns like `M{0,3} # thousands` with inline explanations. Always pass `re.VERBOSE` explicitly—it's easy to forget. - **Abstraction pays off in rule-based systems** (Middle): The pluralization engine evolves from hardcoded if-statements to a generic rule sequence, then to file-driven rules with caching. Each refactor makes adding new rules easier—a lesson in incremental design. - **Assertions are runtime guards, not just tests** (Late): `assert` raises `AssertionError` on false conditions, optionally with a message. The alphametics solver uses it to bail early on impossible puzzles (>10 unique letters). Use asserts for invariants, not user-input validation. ## 【Reading Tips】 - **Skim the installation chapters** (~0%–9%) unless you're setting up Python 3 on a new machine. The editor/IDE discussion is dated—PyDev and Komodo are mentioned, but the community list is the real takeaway. - **Deep-read the regex chapters** (~25%–38%): The progression from compact to verbose patterns is the clearest regex tutorial you'll find. Type every example into IDLE—regex is learned by doing, not reading. - **Work through the pluralization engine twice** (~38%–47%): First read for the concept (rules → abstraction → file-driven), then re-read for the implementation details (caching, `StopIteration`). This is the book's intellectual core. - **Watch for the print edition's missing underscores**: The physical book reportedly omits underscores in code, breaking examples. Use the free online HTML version or PDF instead—the content is identical but the code works. - **Skip the alphametics chapter if pressed for time** (~47%+): It's a fun puzzle, but the assert and `itertools` lessons are covered more concisely elsewhere. ## 【Coverage Limits】 This guide covers the book's progression through data types, strings/encodings, regex, the pluralization case study, and testing. The excerpts do not cover later chapters on files, XML/HTML parsing, HTTP web services, or the comprehensive unit testing framework—those sections are not represented in the source material. ##