Getting Started with Python (Thomas Theis)（Z-Library）

【One-Line Pitch】 A hands-on crash course that takes you from installing Python to building small applications with databases, GUIs, and threads. Best for absolute beginners and self-taught learners who want a single guided path with exercises rather than a reference tome. 【Book Arc】 - **Opening (~0%–12%)**: Environment setup, running your first program, and why Python dominates industry; then variables, numeric types, and the floating-point precision caveat you must internalize early. - **Early (~12%–31%)**: Control flow through branching, loops, and operator precedence, illustrated by small games; then functions, modules, and the core data structures (strings, lists, tuples, dictionaries) plus the identity-vs-equality distinction. - **Middle (~31%–54%)**: Standard library and formatting work — print/format options, math and random modules, custom modules, command-line parameters — followed by object-oriented programming with inheritance, then dates, queues, collections, and multithreading with shared data. - **Late (~54%–end)**: Applied topics: file and directory handling with open modes and seek/close discipline, databases via SQLite and MySQL, and GUI development with PyQt widgets. - **Ending**: A running game-development example threaded across chapters, plus larger practice programs (e.g., a fractions-training exercise) that combine branches, loops, exceptions, tuples, and multi-return functions. 【Key Takeaways】 - **Floating-point numbers are not mathematically exact** (Opening): the book shows a miles-to-kilometers conversion producing a stray digit at the 16th decimal place, and warns this limitation resurfaces throughout — plan to round for display. (Opening) - **Identity and equality are different questions** (Early): `is` checks whether two names reference the same object, `==` checks content; the book demonstrates this with numbers, strings, and lists, where reassignment versus mutation behave differently. (Early) - **Modularization pays off as programs grow** (Early): functions and modules let you define reusable parts once, share them across programs, and keep maintenance tractable — the stated rationale for splitting code early rather than later. (Early) - **Dictionaries are unordered key-value stores** (Early): created with curly braces, compared only by `==`/`!=` on matching pairs, and accessed by key; the book walks through adding, replacing, deleting, and updating entries. (Early) - **Object orientation is taught as specialization** (Middle): a base `Vehicle` class passes properties and methods to a derived `Car` class via inheritance and `super()`, with constructors, destructors, and `__dict__` used for data exchange such as JSON. (Middle) - **Threads share global state, which is both the point and the hazard** (Middle): subthreads access and mutate the main thread's globals, and thread IDs let you observe parallel execution — the book demonstrates the mechanism without dwelling on synchronization. (Middle) - **File handling demands discipline** (Late): opening modes (`a+`, binary `b`) and the access position controlled by `seek()` matter, and files must be closed or they may be blocked from further access. (Late) - **The book closes the loop with integrated practice** (Ending): a fractions-training program with three difficulty levels and a chapter-spanning game example show how branches, loops, exceptions, tuples, and multi-return functions combine in real code. (Ending) 【Reading Tips】 - Deep-read the early chapters on variables, floating-point behavior, and identity vs. equality — these are the conceptual traps that cause silent bugs later. - Skim the standard-library catalog sections (math, random, time, collections) on a first pass, then return when a project actually needs them. - Treat the larger example programs (fractions training, the game) as integration checkpoints: attempt them before reading the solution to test whether the earlier chapters stuck. - For the applied chapters (files, databases, PyQt), type the examples rather than reading them — GUI and database code rarely makes sense passively. - Keep the operator-precedence and built-in function tables as quick references; they are lookup material, not memorization material. 【Coverage Limits】 This guide is based on stratified excerpts covering roughly the first half of the book in detail, with later chapters (files, databases, GUI/PyQt) represented mainly by section headings and brief fragments. Specific later-chapter examples, database schemas, and PyQt widget walkthroughs are not covered in the excerpts.