Re: [flask] Flask Extension Registry Online
- From:
- Dan Jacob
- Date:
- 2010-05-09 @ 13:00
I wonder if some kind of signals API might be useful with extensions.
For example, if you have a flaskext.database extension which requires
getting a database connection with each request, you might have code
like this:
@signals.before_request
def connect_db():
g.db = connect_db()
Alternatively, you might want to attach signals that run at
application start up or shutdown. This would make it easier to hook
extension functionality into your code.
The module-support branch however might be enough to cover at least
some of these cases.
On 9 May 2010 13:13, Armin Ronacher <armin.ronacher@active-4.com> wrote:
> Hi,
>
> The Flask Extension Registry is now online:
> http://flask.pocoo.org/extensions/
>
> If you have extensions for Flask (modules that add extra functionality),
> then follow this guide to get it enlisted:
> http://flask.pocoo.org/extensions/creating/
>
>
> Regards,
> Armin
>
Re: [flask] Flask Extension Registry Online
- From:
- Armin Ronacher
- Date:
- 2010-05-10 @ 05:40
Hi,
On 5/9/10 3:00 PM, Dan Jacob wrote:
> @signals.before_request
> def connect_db():
> g.db = connect_db()
Extensions can already do this:
from flaskext.sqlalchemy import init_sqlalchemy
db_session = init_sqlalchemy(app)
And that funciton would do this:
def init_sqlalchemy(app):
db_session = make_session(...)
@app.after_request
def cleanup(response):
db_session.remove()
return response
return db_session
I don't want to depend on blinker on Flask itself, and I am not sure how
many problems signals would solve over decorators.
Regards,
Armin