|
Original |
Translation |
|
1357
|
Although Django is an MVC-style framework, it names the elements differently, which is described in the `Django FAQ <http://docs.djangoproject.com/en/dev/faq/general/#django-appears-to-be-a-mvc-framework-but-you-call-the-controller-the-view-and-the-view-the-template-how-come-you-don-t-use-the-standard-names>`_.
|
|
|
1358
|
|
|
|
1359
|
Another popular web framework for Python is `TurboGears <http://www.turbogears.org/>`_. TurboGears takes the approach of using already existing components and combining them with glue code to create a seamless experience. TurboGears gives the user flexibility in choosing components. For example the ORM and template engine can be changed to use packages different from those used by default.
|
|
|
1360
|
The documentation can be found in the `TurboGears wiki <http://docs.turbogears.org/>`_, where links to screencasts can be found. TurboGears has also an active user community which can respond to most related questions. There is also a `TurboGears book <http://turbogearsbook.com/>`_ published, which is a good starting point.
|
|
|
1361
|
|
1362
|
|
|
|
1363
|
The Zope framework is one of the "old original" frameworks. Its current incarnation in Zope2 is a tightly integrated full-stack framework. One of its most interesting feature is its tight integration with a powerful object database called the `ZODB <https://launchpad.net/zodb>`_ (Zope Object Database). Because of its highly integrated nature, Zope wound up in a somewhat isolated ecosystem: code written for Zope wasn't very usable outside of Zope, and vice-versa. To solve this problem the Zope 3 effort was started. Zope 3 re-engineers Zope as a set of more cleanly isolated components. This effort was started before the advent of the WSGI standard, but there is WSGI support for Zope 3 from the `Repoze <http://repoze.org/>`_ project. Zope components have many years of production use behind them, and the Zope 3 project gives access to these components to the wider Python community. There is even a separate framework based on the Zope components: `Grok <http://grok.zope.org/>`_.
|
|
|
1364
|
Zope is also the infrastructure used by the `Plone <http://plone.org/>`_ content management system, one of the most powerful and popular content management systems available.
|
|
|
1365
|
|
|
|
1366
|
Of course these are not the only frameworks that are available. There are many other frameworks worth mentioning.
|
|
|
1367
|
Another framework that's already been mentioned is `Pylons`_. Pylons is much like TurboGears, but with an even stronger emphasis on flexibility, which comes at the cost of being more difficult to use. Nearly every component can be exchanged, which makes it necessary to use the documentation of every single component, of which there are many. Pylons builds upon `Paste <http://pythonpaste.org/>`_, an extensive set of tools which are handy for WSGI.
|
|
|
1368
|
And that's still not everything. The most up-to-date information can always be found in the Python wiki.
|
|
|
1369
|
The Python wiki contains an extensive list of `web frameworks <http://wiki.python.org/moin/WebFrameworks>`_.
|
|
|
1370
|
Most frameworks also have their own mailing lists and IRC channels, look out for these on the projects' web sites. There is also a general "Python in the Web" IRC channel on freenode called `#python.web <http://wiki.python.org/moin/PoundPythonWeb>`_.
|
|