Flask Academy · 课时

使用 init_app 初始化扩展

将扩展绑定延迟到应用创建时

使用 init_app 初始化扩展 是 CoddyKit 上的免费 Flask Academy 课时。这是第 3 节课，共 4 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。这是 Flask Academy 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Flask Academy 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

The Extension Dilemma

Extensions like SQLAlchemy used to take the app right away. Inside a factory that does not work, because the app does not exist at import time yet. 🤔

Create Without an App

The fix is two steps. First, create the extension object at module level with no app passed in. It stays unbound for now.

from flask_sqlalchemy import SQLAlchemy
db = SQLAlchemy()  # no app yet

Bind It Later

Second, call init_app inside the factory once the app is built. This binds the extension to that specific instance.

def create_app():
    app = Flask(__name__)
    db.init_app(app)
    return app

Why Two Steps

The extension object can be imported anywhere as a global, while the actual binding waits until the factory chooses a config. Best of both worlds.

Importable Everywhere

Because db lives at module level, your models and views import it freely without touching the app, avoiding circular imports.

from app.extensions import db

A Tidy extensions Module

A common pattern keeps all unbound extensions in one extensions.py file, then the factory imports and inits each one.

db = SQLAlchemy()
migrate = Migrate()
login = LoginManager()

Init Many at Once

Inside create_app you simply call init_app on each extension, passing the same fresh app to all of them.

db.init_app(app)
migrate.init_app(app, db)
login.init_app(app)

Per-App Binding

Because binding happens in the factory, two different apps can each init_app the same extension class independently. Great for tests.

Config Is Read at Init

Extensions read settings like the database URI during init_app, so set those config values before you bind them.

app.config["SQLALCHEMY_DATABASE_URI"] = uri
db.init_app(app)

Use It Within a Context

After init_app, the extension needs an app context to actually run queries, since it must know which app it is talking to.

with app.app_context():
    db.create_all()

The Golden Rule

Create the extension unbound at import, then call init_app in the factory. That single split unlocks the whole pattern. 🔑

Quick Check

Why create an extension object without an app, then call init_app?

Recap

You learned the two-step move: build extensions unbound, then call init_app in the factory. Importable globals plus per-app binding, with no circular imports. 🌟

常见问题解答

「使用 init_app 初始化扩展」课时是免费的吗？

是的 — 「使用 init_app 初始化扩展」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Flask Academy 课程的其余内容，请升级到 CoddyKit PRO。 Flask Academy 课程共包含 4 节课。

「使用 init_app 初始化扩展」这节课中我会学到什么？

将扩展绑定延迟到应用创建时你通过在浏览器中直接运行的动手代码来练习 Flask Academy，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 Flask Academy 需要有经验吗？

无需任何先前经验。CoddyKit 上的 Flask Academy 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。这是第 3 节课，共 4 节。

「使用 init_app 初始化扩展」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 Flask Academy 课中编写并运行代码吗？

能。每节 Flask Academy 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

← 返回 Flask Academy