Extension initialization pattern in Flask - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of the Flask extension initialization pattern?

It allows you to create an extension instance separately and initialize it later with a Flask app. This helps organize code and supports multiple app instances.

beginner

How do you create a Flask extension instance without binding it to an app immediately?

You create the extension object by calling its constructor without passing the app, for example: db = SQLAlchemy().

beginner

What method do you call to bind a Flask extension instance to an app later?

You call the init_app(app) method on the extension instance, passing the Flask app object.

intermediate

Why is the extension initialization pattern useful in Flask applications?

It supports creating extensions before the app exists, helps with testing, and allows sharing one extension instance across multiple apps.

beginner

Show a simple example of the Flask extension initialization pattern using SQLAlchemy.

from flask import Flask
from flask_sqlalchemy import SQLAlchemy

db = SQLAlchemy()  # create extension instance

def create_app():
    app = Flask(__name__)
    app.config['SQLALCHEMY_DATABASE_URI'] = 'sqlite:///test.db'
    db.init_app(app)  # initialize with app
    return app

What does the init_app() method do in Flask extensions?

A Deletes the extension instance

B Creates a new Flask app

C Binds the extension instance to a Flask app

D Runs the Flask app

The init_app() method connects the extension instance to a Flask app, allowing it to work with that app.

Why might you create a Flask extension instance without passing the app immediately?

A Because Flask requires it

B To delay app creation and support multiple apps

C To avoid using extensions

D To make the app run faster

Creating the extension instance first allows you to initialize it later with different apps, useful in app factories and testing.

Which of these is a benefit of the extension initialization pattern?

A Supports multiple Flask apps sharing one extension instance

B Prevents using extensions

C Automatically creates a database

D Removes the need for configuration

This pattern allows one extension instance to be used with many apps by calling init_app() multiple times.

In the extension initialization pattern, when is the extension instance typically created?

A Before the Flask app is created

B After the app runs

C Only inside the app factory

D When the server stops

The extension instance is created first, then later initialized with the app.

What is the common name for the Flask pattern that uses init_app()?

A Decorator pattern

B Blueprint pattern

C Singleton pattern

D Extension initialization pattern

This pattern is called the extension initialization pattern because it initializes extensions separately from app creation.

Explain the Flask extension initialization pattern and why it is useful.

Think about how you can prepare an extension before the app exists.

Write a simple example showing how to use the extension initialization pattern with a Flask app and SQLAlchemy.

Remember to separate extension creation and app creation.