<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Flask on maateen</title><link>https://maateen.me/tags/flask/</link><description>Recent content in Flask on maateen</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 22 Dec 2016 00:00:00 +0000</lastBuildDate><atom:link href="https://maateen.me/tags/flask/index.xml" rel="self" type="application/rss+xml"/><item><title>Would Instagram Use Flask Today?</title><link>https://maateen.me/posts/if-instagram-would-start-today-would-they-use-flask/</link><pubDate>Thu, 22 Dec 2016 00:00:00 +0000</pubDate><guid>https://maateen.me/posts/if-instagram-would-start-today-would-they-use-flask/</guid><description>&lt;p&gt;Before that, you should know the main difference between Flask and Django. Both are famous in Python arena. But they have different necessity and outlook.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://flask.pocoo.org/"&gt;Flask&lt;/a&gt; is a microframework. The &amp;ldquo;micro&amp;rdquo; in microframework means Flask aims to keep the core simple but extensible. Flask won&amp;rsquo;t make many decisions for you, such as what database to use.&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.djangoproject.com/"&gt;Django&lt;/a&gt; comes with batteries-included. Django takes care of much of the hassle of Web development, so you can focus on writing your app without needing to reinvent the wheel.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Project like Instagram needs a lot of features, surely. You can go with Flask but there you have to extend it with many extensions and third-party modules. But Django gives you everything in one package. Django includes dozens of extras you can use to handle common Web development tasks. Django takes care of user authentication, content administration, site maps, RSS feeds, and many more tasks — right out of the box. Besides, Django has more third-party packages than Flask. That&amp;rsquo;s the power I think.&lt;/p&gt;</description></item><item><title>Should You Use SQLite in a Flask App?</title><link>https://maateen.me/posts/is-it-good-idea-to-have-sqlite-database-in-flask-app/</link><pubDate>Sun, 10 Jul 2016 00:00:00 +0000</pubDate><guid>https://maateen.me/posts/is-it-good-idea-to-have-sqlite-database-in-flask-app/</guid><description>&lt;p&gt;SQLite is an in-process library that implements a &lt;a href="https://www.sqlite.org/selfcontained.html"&gt;self-contained&lt;/a&gt;, &lt;a href="https://www.sqlite.org/serverless.html"&gt;serverless&lt;/a&gt;, &lt;a href="https://www.sqlite.org/zeroconf.html"&gt;zero-configuration&lt;/a&gt;, &lt;a href="https://www.sqlite.org/transactional.html"&gt;transactional&lt;/a&gt; SQL database engine. Unlike most other SQL databases, SQLite does not have a separate server process. SQLite reads and writes directly to ordinary disk files. A complete SQL database with multiple tables, indices, triggers, and views, is contained in a single disk file. The database &lt;a href="https://www.sqlite.org/fileformat2.html"&gt;file format&lt;/a&gt; is cross-platform - you can freely copy a database between 32-bit and 64-bit systems or between &lt;a href="http://en.wikipedia.org/wiki/Endianness"&gt;big-endian&lt;/a&gt; and &lt;a href="http://en.wikipedia.org/wiki/Endianness"&gt;little-endian&lt;/a&gt; architectures. These features make SQLite a popular choice as an &lt;a href="https://www.sqlite.org/appfileformat.html"&gt;Application File Format&lt;/a&gt;. When you&amp;rsquo;re gonna use SQLite as database for your Flask app, then you have to consider some things:&lt;/p&gt;</description></item><item><title>Is Python Flask Only for Websites?</title><link>https://maateen.me/posts/is-python-flask-only-for-web-sites/</link><pubDate>Tue, 31 May 2016 00:00:00 +0000</pubDate><guid>https://maateen.me/posts/is-python-flask-only-for-web-sites/</guid><description>&lt;h3 class="heading" id="what-is-flask"&gt;
 What is Flask?
 &lt;a class="anchor" href="#what-is-flask"&gt;#&lt;/a&gt;
&lt;/h3&gt;
&lt;p&gt;Flask is a microframework for Python based on Werkzeug, Jinja 2 and good intentions. And before you ask: It&amp;rsquo;s &lt;a href="http://flask.pocoo.org/docs/license/"&gt;BSD licensed&lt;/a&gt;!&lt;/p&gt;
&lt;p&gt;&amp;ldquo;Micro&amp;rdquo; does not mean that your whole web application has to fit into a single Python file (although it certainly can), nor does it mean that Flask is lacking in functionality. The &amp;ldquo;micro&amp;rdquo; in microframework means Flask aims to keep the core simple but extensible. Flask won&amp;rsquo;t make many decisions for you, such as what database to use. Those decisions that it does make, such as what templating engine to use, are easy to change. Everything else is up to you, so that Flask can be everything you need and nothing you don&amp;rsquo;t.&lt;/p&gt;</description></item><item><title>Django vs Flask: Which Should You Use?</title><link>https://maateen.me/posts/which-python-web-framework-is-better-django-or-flask/</link><pubDate>Mon, 14 Mar 2016 00:00:00 +0000</pubDate><guid>https://maateen.me/posts/which-python-web-framework-is-better-django-or-flask/</guid><description>&lt;p&gt;This question was asked on &lt;a href="https://www.quora.com/Which-Python-web-development-framework-is-better-Django-or-Flask"&gt;Quora&lt;/a&gt;. When I see the question, I set my mind to answer the question. I know I have a little experience on this section but I have tried my level best. Please never forget to mention if I miss anything or make any wrong. By the way, the answer of this question should be aim depended. Please let me explain.&lt;/p&gt;
&lt;h3 class="heading" id="job-aimed"&gt;
 Job aimed
 &lt;a class="anchor" href="#job-aimed"&gt;#&lt;/a&gt;
&lt;/h3&gt;
&lt;p&gt;You will find that most of the Python Web Developing companies are using &lt;a href="https://www.djangoproject.com/"&gt;Django&lt;/a&gt;. Obviously they get maximum benefits from it like easy or resourceful. Whatever, as Django is preferred by them, you may have to go with them to get a job.&lt;/p&gt;</description></item></channel></rss>