|
45 | 45 | <div class="row"> |
46 | 46 | <div class="col-md-8"> |
47 | 47 | <h1>Flask</h1> |
48 | | -<p><a href="http://flask.pocoo.org/">Flask</a> is a Python microframework deliberately |
49 | | -built with a |
50 | | -<a href="http://flask.pocoo.org/docs/design/">small core and easy-to-extend philosophy</a>. |
51 | | -Flask is generally considered more |
| 48 | +<p><a href="http://flask.pocoo.org/">Flask</a> is a Python web framework built with a |
| 49 | +<a href="http://flask.pocoo.org/docs/design/">small core and easy-to-extend philosophy</a>. </p> |
| 50 | +<h2>Why is Flask a good web framework choice?</h2> |
| 51 | +<p>Flask is generally considered more |
52 | 52 | <a href="http://stackoverflow.com/questions/58968/what-defines-pythonian-or-pythonic">Pythonic</a> |
53 | | -than Django because Flask web application code is often more |
54 | | -explicit. Flask was also written several years after Django and therefore |
| 53 | +than Django because Flask web application code is by and large more explicit. |
| 54 | +Flask is easy to get started with as a beginner because there is little |
| 55 | +boilerplate code for getting a simple app up and running. </p> |
| 56 | +<p>For example, here's a valid "hello world" web application with Flask (the |
| 57 | +equivalent in Django would be significantly more code):</p> |
| 58 | +<div class="codehilite"><pre><span class="n">from</span> <span class="n">flask</span> <span class="n">import</span> <span class="n">Flask</span> |
| 59 | +<span class="n">app</span> <span class="o">=</span> <span class="n">Flask</span><span class="p">(</span><span class="n">__name__</span><span class="p">)</span> |
| 60 | + |
| 61 | +<span class="err">@</span><span class="n">app</span><span class="p">.</span><span class="n">route</span><span class="p">(</span><span class="sc">'/'</span><span class="p">)</span> |
| 62 | +<span class="n">def</span> <span class="n">hello_world</span><span class="p">()</span><span class="o">:</span> |
| 63 | + <span class="k">return</span> <span class="err">'</span><span class="n">Hello</span> <span class="n">World</span><span class="o">!</span><span class="err">'</span> |
| 64 | + |
| 65 | +<span class="k">if</span> <span class="n">__name__</span> <span class="o">==</span> <span class="err">'</span><span class="n">__main__</span><span class="err">'</span><span class="o">:</span> |
| 66 | +<span class="n">app</span><span class="p">.</span><span class="n">run</span><span class="p">()</span> |
| 67 | +</pre></div> |
| 68 | + |
| 69 | + |
| 70 | +<p>Flask was also written several years after Django and therefore |
55 | 71 | learned from the Python community's reactions as the framework evolved. |
56 | 72 | Jökull Sólberg wrote a great piece articulating to this effect in his |
57 | 73 | <a href="http://jokull.calepin.co/my-flask-to-django-experience.html">experience switching between Flask and Django</a>.</p> |
|
0 commit comments