@@ -61,8 +61,6 @@ project as-is, or customized to fit your needs.
6161There are annual Django conferences `in the United States
6262<http://djangocon.us> `_ and `in Europe <http://djangocon.eu >`_.
6363
64- The majority of new Python web applications today are built with Django.
65-
6664Flask
6765-----
6866
@@ -85,9 +83,6 @@ For those that do, there are many
8583`Extensions <http://flask.pocoo.org/extensions/ >`_ available that may
8684suit your needs. Or, you can easily use any library you want yourself!
8785
88- Flask is default choice for any Python web application that isn't a good
89- fit for Django.
90-
9186
9287Tornado
9388--------
@@ -102,14 +97,18 @@ I do not recommend using Tornado unless you think you need it.
10297Pyramid
10398--------
10499
105- `Pyramid <http://www.pylonsproject.org/ >`_ is a lot like Django, except
106- with a heavier focus on modularity. It comes with a smaller number of
107- libraries ("batteries") built-in, and encourages users to extend its
108- base functionality.
100+ `Pyramid <http://www.pylonsproject.org/ >`_ lies somewhere between a big
101+ framework like Django and the microframeworks: It comes with a lot of libraries
102+ and functionality and can thus not be considered lightweight. On the other
103+ hand, it does not provide all the functionality Django does. Instead Pyramid
104+ brings basic support for most regular tasks and provides a great deal of
105+ extensibility. Additionally, Pyramid has a huge focus on complete
106+ `documentation <http://docs.pylonsproject.org/en/latest/docs/pyramid.html >`__
107+ and boast 100% unittest coverage.
108+
109+ **Support ** can also be found in the
110+ `documentation <http://docs.pylonsproject.org/en/latest/index.html#support-desc >`__.
109111
110- Pyramid does not have a large user base, unlike Django and Flask. It's a
111- capable framework, but not a very popular choice for new Python web
112- applications today.
113112
114113Web Servers
115114:::::::::::
0 commit comments