Differences between revisions 90 and 91
Revision 90 as of 2007-09-12 11:19:45
Size: 14715
Editor: 147
Comment:
Revision 91 as of 2007-09-12 11:20:49
Size: 14725
Editor: 147
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
A Web framework is a collection of packages or modules which allow developers to write Web applications (see WebApplications) or services without having to handle such low-level details as protocols, sockets or process/thread management. As a developer using a framework, you typically write code which conforms to some kind of conventions, with the benefit being that most of the code can be concerned with the logic of the application, rather than working out how to process incoming network messages, spawn processes, work out which part of the application should be invoked, and so on. A Web framework is a collection of packages or modules which allow developers to write Web applications (see WebApplications) or services without having to handle such low-level details as protocols, sockets or process/thread management.
Line 7: Line 7:
Some packages can be considered 'components' in that they provide abstractions only for certain things (eg. incoming requests, outgoing responses, state handling), whereas packages can be described as 'frameworks' as they provide many more abstractions and mechanisms (eg. database access, presentation of Web pages). Since a non-trivial Web application will require a number of different kinds of abstractions, often stacked upon each other, those frameworks which attempt to provide a complete solution for applications are often known as "full-stack" frameworks in that they attempt to supply components for each layer in the stack. As a developer using a framework, you typically write code which conforms to some kind of conventions, with the benefit being that most of the code can be concerned with the logic of the application, rather than working out how to process incoming network messages, spawn processes, work out which part of the application should be invoked, and so on.

Some packages can be considered 'components' in that they provide abstractions only for certain things (eg. incoming requests, outgoing responses, state handling).

Some other packages can be described as 'frameworks' as they provide many more abstractions and mechanisms (eg. database access, presentation of Web pages). Since a non-trivial Web application will require a number of different kinds of abstractions, often stacked upon each other, those frameworks which attempt to provide a complete solution for applications are often known as "full-stack" frameworks in that they attempt to supply components for each layer in the stack.

Web Frameworks for Python

A Web framework is a collection of packages or modules which allow developers to write Web applications (see WebApplications) or services without having to handle such low-level details as protocols, sockets or process/thread management.

As a developer using a framework, you typically write code which conforms to some kind of conventions, with the benefit being that most of the code can be concerned with the logic of the application, rather than working out how to process incoming network messages, spawn processes, work out which part of the application should be invoked, and so on.

Some packages can be considered 'components' in that they provide abstractions only for certain things (eg. incoming requests, outgoing responses, state handling).

Some other packages can be described as 'frameworks' as they provide many more abstractions and mechanisms (eg. database access, presentation of Web pages). Since a non-trivial Web application will require a number of different kinds of abstractions, often stacked upon each other, those frameworks which attempt to provide a complete solution for applications are often known as "full-stack" frameworks in that they attempt to supply components for each layer in the stack.

High Level Full-Stack Frameworks

A web application may use a combination of a base HTTP application server, a storage mechanism such as a database, a template engine, a request dispatcher, an authentication module and an AJAX toolkit. These can be individual components or be provided together in a high-level framework.

These are the main high-level frameworks. Many of them include components listed further down the page.

  • ["Django"] (0.96 Released 2007-03-23) a high-level Python Web framework that encourages rapid development and clean, pragmatic design
  • [http://pylonshq.com/ Pylons] (0.9.6 Released 2007-08) a lightweight Web framework emphasizing flexibility and rapid development. It combines the very best ideas from the worlds of Ruby, Python and Perl, providing a structured but extremely flexible Python Web framework. It's also one of the first projects to leverage the emerging WSGI standard, which allows extensive re-use and flexibility but only if you need it. Out of the box, Pylons aims to make Web development fast, flexible and easy. Pylons is built on top of Paste (see below).

  • [http://www.turbogears.org/ TurboGears] (1.0 Released 2007-01-03) the rapid Web development megaframework you've been looking for. Combines ["CherryPy"], Kid, SQLObject and MochiKit. After reviewing the website check out: [http://lucasmanual.com/mywiki/TurboGears QuickStart Manual]

  • [http://www.zope.org/ Zope] (2.10.3 Released 2007-03-25, 3.3.1 Released 2007-01-14) a server for building ContentManagementSystems, intranets, portals, and custom applications.

Templating Engines

Templating engines allow you to separate your application code from the presentation. Many of these engines can be used alone or within a high-level framework.

  • [http://www.myghty.org/ Myghty ] (1.0 Released 2006-01-27) is a Python based templating framework originally based on HTML::Mason

  • [http://www.makotemplates.org/ Mako] is an all-new templating engine which represents the best ideas of Myghty distilled into a completely-rewritten and updated API and syntax.

  • [http://www.thomas-lotze.de/en/software/ophelia/ Ophelia] (0.3 Released 2007-07-06) Generates XHTML pages from TAL templates. This avoids repetitive code, allows the site content to reside in the file system instead of a database, and lets Python scripts make the content dynamic.

  • ["JonsPythonModules"] (1.06 Released 2004-04-11) a set of simple yet powerful multi-threaded object-oriented CGI/FastCGI/mod_python/html-templating modules for Python

  • [http://www.cheetahtemplate.org/ Cheetah] - Cheetah is a Python-powered template engine and code generator. It may be used as a standalone utility or combined with other tools.

  • [http://genshi.edgewall.org/ Genshi] is a Python library that provides an integrated set of components for parsing, generating, and processing HTML, XML or other textual content for output generation on the web.

HTTP frameworks

The packages provide the base 'application server', either running as its own independent process or upon Apache. You can then bring your own applications, templating engines and other components to run on top of it.

  • ["CherryPy"] (3.0.2 Released 2007-08-07) is a pythonic, object-oriented HTTP framework. CherryPy powered web applications are in fact stand-alone Python applications embedding their own multi-threaded web server.["TurboGears"] (see above) also uses CherryPy.

  • [http://pythonpaste.org/ Python Paste] (1.4 Released 2007-06-26) brings consistency to Python Web development and Web application installation, providing tools for both developers and system administrators. Also, Pylons (see above) is built on top of Paste.

  • [http://www.movatis.com/crusader Crusader] is a powerful application server for Python based upon a scaleable, extensible and easy-to-use general purpose server framework.

  • ["Karrigell"] (2.3.3 Released 2007-01-15) is a flexible Python web framework, with a clear and intuitive syntax. It is independent from any database, ORM or templating engine, and lets the programmer choose between a variety of coding styles.
  • SkunkWeb (3.4.0 Released 2004-09-10)

Authorisation toolkits

These allow you to add authorisation to your web applications.

Content Management Systems

Some CMS' allow you to build application like functionality upon them. See ContentManagementSystems for more details.

Other Frameworks/components

These components are not categorised at the moment:

  • ["4Suite"] (XML-1.0rc3 Released 2006-08-28)
  • [http://www.stackworks.net/view.php/cymbeline/index.html Cymbeline] (1.3.1 Released 2005-12-09) an application server framework, including functionality such as DB and arbitrary object pooling, Web servers, persistant object repository, and a text console

  • [http://gizmojo.org/ Gizmo(QP)] (0.7 Released 2007-04-17) extends QP (see below) adding functionality to help with building rich and exacting web interfaces. Includes a Form module that supports (redundant) automatically generated client-side field validation as well as additional json callbacks.

  • [https://www.mems-exchange.org/software/qp/ QP] (1.8 Released 2006-08-22) a package for defining and running multiple Web applications that are based on Durus for persistence, offering standard persistent Session and User classes, easy interactive database sessions, and unicode QPY for assembling html.

  • ["Spyce"] (2.1.3 Released 2006-11-17)
  • [http://webpy.org/ web.py] (0.2 Released 2006-11-27) Think about the ideal way to write a Web app. Write the code to make it happen.

  • [http://www.webwareforpython.org/ Webware] (0.9.4 Released 2007-07-07) is a suite of Python packages and tools for developing object-oriented, Web-based applications

  • ["Albatross"] (1.35 Released 2006-06-20) a small and flexible Python toolkit for developing highly stateful Web applications.
  • ["Aquarium"] (2.2.1 Released 2005-04-21) offers convenient libraries, tight integration with Cheetah, adaptors for various Web environments
  • BaseHttpServer (along with successors such as DocXmlRpcServer) can be considered as the original Python Web framework

  • [http://divmod.org/trac/wiki/DivmodNevow Divmod Nevow] (0.9.0 Released 2006-06-12) a comprehensive library including a resource model encouraging the separation of application and presentation logic, a markup system with support for designer-friendly XHTML templates and pure-Python templates, and a robust AJAX-like API ([http://divmod.org/trac/wiki/DivmodNevow/Athena Divmod Athena]) which supports the creation of highly dynamic Web pages in a structured manner.

  • ["JOTWeb2"] (1.10 Released 2005-12-30) developing dynamic Web applications using HTML and TAL/TALES/METAL for templating
  • ["maki"]
  • [http://nick.borko.org/pse/index.html Python Servlet Engine] (3.0.4 Released 2006-02-17) PSE parses your templates into byte compiled "servlets" to produce Web pages that run fast

  • [http://www.stroeder.com/pylib/PyWebLib/ PyWebLib] (1.3.4) - provides support for forms and sessions; used to implement web2ldap

  • [http://www.mems-exchange.org/software/quixote/ Quixote] (2.4 Released 2005-12-13) Allows developers to develop dynamic Web sites while using as much of their existing Python knowledge as possible

  • [http://snakelets.sourceforge.net/ Snakelets] (1.44 Released 2006-06-04) simple-to-use Python Web application server

  • [http://trac.pytan.com/ Spark] (0.2.1 Released 2006-9-15) Fast and lightweight Web kit. Supports mod_python, WSGI, Twisted.

  • [http://robinparmar.com/wasp.html Wasp] (2.00 Released 2007.07) - supports command-line, CGI and embedded web server modes, with templating, session mechanism and other modules emphasizing ease of use and familiar paradigms.

  • ["WebStack"] (1.2.4 Released 2007-06-13) - very lightweight, requiring layers of extra technology (eg. [http://www.python.org/pypi/XSLTools XSLTools] and others) to match full-stack frameworks in feature comparisons

Popularity

Due to its established presence in Python Web programming, ["Zope"] and related solutions remain popular. Other full-stack frameworks which have enjoyed more recent popularity include ["TurboGears"] and ["Django"]. Measures of popularity include things like the number of subscribers & messages a project's e-mail lists or Internet groups may have, and such information can be readily discovered through services such as Google Groups. For example, as of 2007-09-07, ordered by recent activity:

Note that some projects' lists or groups may not be available through such services, and active contributions to a discussion group are not necessarily indicative of the level of production usage or development of a project.

Frameworks in Books

These frameworks are not apparently available for download, but are covered in various books:

  • ["Slither"]

Books and Articles

Comparisons and Tests

Editorial Notes

The above lists should be arranged in ascending alphabetical order - please respect this when adding new frameworks. The distinction made between "full-stack" and "lightweight" frameworks is difficult to make - please feel free to relocate frameworks to other lists, but please only do so if you actually know as a user or developer of that framework that the framework is miscategorised. When specifying release dates please use the format YYYY-MM-DD.

Notes on Editing Framework Pages

  • Opinions based on experience are welcome, but framework or templating system authors should sign their comments with InTheirOwnWords to admit to a certain bias.

  • The rather strict format of the main entries (described in WebProgrammingTemplateHelp) should not been seen as a limit. Feel free to add new pages containing examples, direct comparisons etc.

  • When adding new entries choose WebProgrammingTemplate when creating the page.

Note

This page does not attempt to list every single Python Web framework that exists or has ever existed, nor does it provide measures of popularity or selection criteria, although the "Popularity" and "Comparisons and Tests" sections provide some additional information along with links to other useful resources.

Be warned that some of the frameworks listed may not be longer actively maintained.

WebFrameworks (last edited 2024-03-20 14:10:26 by CoMelissant)

Unable to edit the page? See the FrontPage for instructions.