init_app() and unit testing about flask-admin

[mrjoes]

I see. You create new application object, but what forbids you to create
new Admin class instance as well?

Idea was to prevent reinitialization of the Admin class after it was
associated with Flask app.

I you see a problem with this approach, can you provide a use case?

28.05.2012 11:14 пользователь "ivirabyan" <
[email protected]>
написал:

I'm using application factory, and as a result, using admin.init_app()
method inside of create_app function. Unit tests create a new app app on
each run, so that init_app gets called multiple times. The problem is that
it raises on second run:
Exception: Flask-Admin is already associated with an application

Application fabrics are widely used for unittesting, and another
extensions, like flask-sqlalchemy allow reinitialization with another app.
For now I hack this like this:
admin.app = None
admin.init_app(app)

---

Reply to this email directly or view it on GitHub:
mrjoes/flask-admin#22

[ivirabyan]

admin class instance created at module level, so that it is available to other modules. Just like db instance of sqlalchemy. See an example:

app.py:

db = SQLAlchemy()
admin = Admin()

def create_app(config=None):
    app = Flask(__name__)
    if config is not None:
        app.config.from_object(config)

    db.init_app(app)
    admin.init_app(app)
    return app

views.py:

from app import db
...

admin.py:

from app import admin
...
admin.add_view(ModelView(Banner, db.session))

Of course I can move admin.add_view() to create_app, but there are too much calls, and I want to keep my create_app() clean. Admin stuff should lie in admin.py