Reputation: 31199
Does Flask framework support MVC pattern naturally? What the part of application should I consider as a model, what as a view and what as a controller?
Typically (in my experience) a Flask app looks like this:
main_dir--|
|
app1--|
| |
| __init__.py
| api.py
| models.py
|
static--|
| |
| all the static stuff
|
app.py # with blueprints registering
Upvotes: 26
Views: 47530
Reputation: 29
Also, take a look at this. It is a small flask-based MVC structure project, and works just fine.
Upvotes: 1
Reputation: 51
To look at Flask from a MVC perspective, I think Flask gives us flexibility to implement our own Model or Views. But for the Controller we need to rely on the Flask framework itself.
1. @app.route("/")
2. def hello():
2.1 # Code for your model here
2.2 # model code
3. return render_template('index.html', username="John Doe")
In the above code -
Upvotes: 4
Reputation: 14591
Flask is actually not an MVC framework. It is a minimalistic framework which gives you a lot of freedom in how you structure your application, but MVC pattern is a very good fit for what Flask provides, at least in the way that MVC pattern is understood today in the context of web applications (which purists would probably object to).
Essentially you write your methods and map them to specific route, e.g.:
@app.route("/")
def hello():
return "Hello World!"
No view or model there, as you can see. However, it is also built on top of Jinja2 template library, so in a realistic app, your method (which acts as a controller) looks like:
@app.route("/")
def hello():
return render_template('index.html', username="John Doe")
Here, you use index.html
template to render the page. That is your view now.
Flask doesn't prescribe any model. You can use whatever you want - from complex object models (typically with using some ORM like SQLAlchemy) to simplest thing which fits your needs.
And there you have it: MVC
Upvotes: 30