|
|
@ -27,7 +27,7 @@ writing reusable :doc:`blueprints </blueprints>` or |
|
|
|
import at all. |
|
|
|
import at all. |
|
|
|
|
|
|
|
|
|
|
|
Flask solves this issue with the *application context*. Rather than |
|
|
|
Flask solves this issue with the *application context*. Rather than |
|
|
|
referring to an ``app`` directly, you use the the :data:`current_app` |
|
|
|
referring to an ``app`` directly, you use the :data:`current_app` |
|
|
|
proxy, which points to the application handling the current activity. |
|
|
|
proxy, which points to the application handling the current activity. |
|
|
|
|
|
|
|
|
|
|
|
Flask automatically *pushes* an application context when handling a |
|
|
|
Flask automatically *pushes* an application context when handling a |
|
|
|