forked from orbit-oss/flask
Reword 0.9 upgrade doc, thanks to plaes on #pocoo.
This commit is contained in:
parent
b885edf810
commit
10c34e6652
1 changed files with 6 additions and 5 deletions
|
|
@ -34,11 +34,12 @@ the old behavior, you can add it easily by subclassing Flask::
|
||||||
return self.response_class(*rv)
|
return self.response_class(*rv)
|
||||||
return Flask.make_response(self, rv)
|
return Flask.make_response(self, rv)
|
||||||
|
|
||||||
If you have an extension that was using :data:`~flask._request_ctx_stack`
|
If you maintain an extension that was using :data:`~flask._request_ctx_stack`
|
||||||
before, please consider changing to :data:`~flask._app_ctx_stack` if it
|
before, please consider changing to :data:`~flask._app_ctx_stack` if it makes
|
||||||
makes sense for your extension. This will for example be the case for
|
sense for your extension. For instance, the app context stack makes sense for
|
||||||
extensions that connect to databases. This will allow your users to
|
extensions which connect to databases. Using the app context stack instead of
|
||||||
easier use your extension with more complex use cases outside of requests.
|
the request stack will make extensions more readily handle use cases outside of
|
||||||
|
requests.
|
||||||
|
|
||||||
Version 0.8
|
Version 0.8
|
||||||
-----------
|
-----------
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue