Python Web开发案例教程：使用Flask、Tornado、Django 慕课版 (南淑萍 王莉丽 王秀友 主编 凌启东 林金珠 副主编)（Z-Library）

# Python Web开发案例教程：使用Flask、Tornado、Django 慕课版 ## 【One-Line Pitch】 A hands-on, case-driven textbook that teaches Python web development through six complete projects built with Flask, Tornado, and Django — ideal for beginners and students who learn best by building real applications rather than studying abstract theory. ## 【Book Arc】 - **Opening (~0%–10%)**: Introduces web development fundamentals — how static pages work, the evolution from CGI to scripting languages like PHP/ASP/JSP, and the basics of HTML, CSS, and JavaScript. This stage builds the prerequisite knowledge needed before touching any Python framework. - **Early (~10%–23%)**: Covers the three core frameworks — Flask, Django, and Tornado — in parallel. Readers learn routing, URL construction with `url_for()`, Jinja2 templating (macros, inheritance, includes), Django's project/App structure and form handling, and Tornado's async foundations. The chapter emphasizes that these frameworks share common concepts. - **Early (~23%–32%)**: First complete case study — a Flask-based online notebook application. Walks through environment setup, MySQL database design with PyMySQL, user registration/login with session management, and CRUD operations for notes. Introduces the `is_logged_in` decorator pattern for protecting routes. - **Middle (~32%–48%)**: Second Flask project — a music website called "甜橙音乐网." Demonstrates modular project organization with blueprints, Flask-SQLAlchemy ORM models, pagination, search functionality, artist/song browsing, and a jPlayer-based audio player. Also covers database relationships (one-to-many) and the Flask-SQLAlchemy setup pattern. - **Late (~48%–100%)**: The remaining chapters (based on the table of contents) continue with a Flask-based shopping system, a Flask travel website ("e起去旅行"), a Tornado-based BBS Q&A community with Redis and long-polling, and a Django project. Each case follows the same structure: requirements analysis → system design → database design → module implementation. ## 【Key Takeaways】 - **Web fundamentals matter before frameworks** (Opening): Understanding how HTTP requests flow through CGI and scripting languages to produce dynamic HTML gives you the mental model needed to debug any web framework issue later. - **The three frameworks share a common core** (Early): Flask, Django, and Tornado all use virtual environments, pip installation, routing, and templates. Learn one well and the others become variations on familiar themes — the book explicitly encourages this cross-framework thinking. - **Jinja2 templating is powerful and reusable** (Early): Macros, template inheritance, and `{% include %}` let you avoid repeating HTML. The `{% block %}` system works like class inheritance in Python, enabling clean base templates that child pages extend. - **Decorators are the clean way to protect routes** (Early): Instead of copy-pasting session checks into every view function, the `is_logged_in` decorator wraps protected routes and redirects unauthenticated users to login — a pattern you'll reuse in every Flask project. - **Flask-SQLAlchemy turns database work into Python** (Middle): Defining models as classes with `db.Column` fields, then using `db.create_all()` to generate tables, eliminates raw SQL for basic operations. Relationships like one-to-many are declared with `db.relationship()` and `db.ForeignKey()`. - **Blueprints keep Flask projects organized** (Middle): The music website shows how to structure a growing Flask app into modular packages (home, admin, etc.), making the codebase maintainable as features multiply. - **Pagination and search are solved problems** (Middle): The `paginate()` method on SQLAlchemy queries handles page-based navigation, and search modules follow a predictable pattern — get query parameters, filter, render results. - **Each framework fits different use cases** (Early): Tornado's async non-blocking I/O suits long-lived connections like WebSockets and chat applications, while Flask's simplicity fits smaller projects and Django's batteries-included approach suits larger, structured applications. ## 【Reading Tips】 - **Skim Chapter 1 if you already know web basics** — the HTML/CSS/JavaScript review is standard material; jump straight to Chapter 2 where the frameworks begin. - **Deep-read the first Flask case study (Chapter 3)** — it establishes the pattern (database → auth → CRUD → templates) that all subsequent projects follow. Master the decorator and session patterns here. - **Pay attention to the "技术准备" (technical preparation) sections** — each case study introduces one or two new tools (Flask-Script, Flask-SQLAlchemy, Redis, long-polling). These are the real learning increments between projects. - **Don't skip the database design sections** — the table structures and relationships are the backbone of each project. Understanding why tables are designed a certain way will help you more than copying the code. - **Use the accompanying MOOC videos for the trickier parts** — the book is designed to pair with online video lectures and quizzes at rymooc.com, which is especially helpful for the Tornado async concepts and the more complex shopping cart logic. ## 【Coverage Limits】 This guide is based on excerpts covering roughly the first half of the book (through the music website case). The later chapters — the Flask shopping system, Flask travel site, Tornado BBS, and Django project — are summarized from the table of contents only and not covered in detail here. ##