Differences between revisions 258 and 259
Revision 258 as of 2006-04-10 09:04:36
Size: 13549
Editor: nrth-cache-2
Comment:
Revision 259 as of 2006-04-11 10:09:52
Size: 13550
Editor: 218
Comment:
Deletions are marked like this. Additions are marked like this.
Line 206: Line 206:
-- StephenWaterbury -- StephenWaterbury.

Web Programming in Python

This topic guide links to the frameworks and templating systems available for Web programming in Python. When deciding to develop Web applications or services, you would usually choose a solution from the list below and then possibly hook it up with a templating system and other components such as database access toolkits, if the solution doesn't provide them - some such as Zope provide virtually everything you can think of!

Python-based Solutions

The listing is up-to-date as of 2005-09-24

Standardisation and Standardisation Proposals

Web Servers

Application Framework Collections

Collection of other projects that have been glued together to provided a feature rich library, without reinventing the wheel.

Application Frameworks

  • ["Albatross"] (1.33 Released 12/16/05)Albatross is a small and flexible Python toolkit for developing highly stateful web applications.
  • ["Aquarium"] (2.2.1 Released 04/21/05)offers convenient libraries, tight integration with Cheetah, adaptors for various Web environments
  • CherryPy (2.2.0 Released 01/27/06)CherryPy is a pythonic, object-oriented web development framework

  • ["Cymbeline"] (1.3.1 Released 12/09/05)application server framework, including functionality such as DB and arbitrary object pooling, web servers, persistant object repository, and a text console
  • [http://divmod.org/trac/wiki/DivmodNevow Divmod Nevow] (0.7.0 Released 12/02/05) 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.

  • ["Django"] (.91 Released 01/11/06)Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design
  • ["JOTWeb2"] (1.10 Released 12/30/05)developing dynamic web applications using HTML and TAL/TALES/METAL for templating
  • ["JonsPythonModules"] (1.06 Released 04/11/04) is a set of simple yet powerful multi-threaded object-oriented CGI/FastCGI/mod_python/html-templating modules for Python

  • ["Karrigell"] (2.2.3 Released 03/26/06) designed to be really simple to use : integrated web server and data base
  • [http://www.myghty.org/ Myghty ] (1.0 Released 01/27/06)Web application framework originally ported from HTML::Mason

  • [http://pythonpaste.org/ Python Paste ] (0.4.1 Released 02/18/06)brings consistency to Python web development and web application installation, providing tools for both developers and system administrators

  • [http://nick.borko.org/pse/index.html Python Servlet Engine] (3.0.4 Released 02/17/06)PSE parses your templates into byte compiled "servlets" to produce web pages that run fast

  • PythonWeb (0.6 Released 08/07/05)provide modules for all the common needs of web developers where components can be used together or independently

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

  • [http://snakelets.sourceforge.net/ Snakelets] (1.43 Released 12/03/05)simple-to-use Python web application server

  • [http://webpy.org/ web.py] (.137 Released 03/27/06)Think about the ideal way to write a web app. Write the code to make it happen

  • [http://www.webwareforpython.org/ Webware] (.9 Released 11/13/05)is a suite of Python packages and tools for developing object-oriented, web-based applications

  • [http://www.zope.org/ Zope] (2.9 Released 01/07/06)server for building content management systems, intranets, portals, and custom applications

Server-embedded Python

Web-based XML processing engines

  • ["4Suite"]
  • ["maki"]

Anchor(TemplatingEngines)

Templating Engines

There are many, many different HTML/XML templating libraries for Python that provide different feature sets and syntaxes. These libraries usually assume that you know how to write HTML or XML.

The number of libraries is so great because such libraries are pretty easy to write in Python; [http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/52305 this recipe from the Python Cookbook] shows how easy it is.

HTML Shorthand Processors

The libraries in this section implement simpler markup languages that can be automatically converted to HTML. This lets you avoid having to write HTML by hand.

HTML Generation class libraries

Static Website Generators

Static website generators are more then [#TemplatingEngines] in that they create the whole site structuire, not just individual files. While templating is an important part of their function, determining the site structure and incorporating structural information in the output (for ex. to automatically generate navigational elements) is what really makes a static website generator a useful tool.

Jython-accessible Java Templating Engines

CPython-accessible C Templating Engines

Utility modules

Related Links

See also:

Books and articles:

Historical information:

Notes on Editing

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.

To Do

  • The templating systems should really get a different page layout, showing examples etc.
  • Describe PHP and Java in the same format as quite a few will want to compare to them anyway
  • Is there any interest in a WebProgrammingShootOut?

Editor: DanielDittmar (this means only that I will adapt the entries to changes in the WebProgrammingTemplate and that I will try to keep the version entries current)

Discussion

For a set of comparisons of my real-world experiences with a bunch of the web solutions described on this page, check my WebSolutionComparison page. These are NOT impartial and unbiased comparisons; these are my personal experiences from building real web sites. Feel free to add your own comparisons.

-- TimRoberts

Wait- I don't understand-

Why were BaseHttpServer, DocXmlRpcServer, CgiScripts taken out?

I'd think that on a page on WebProgramming, those things would be listed.

-- LionKimbro DateTime(2004-08-02T14:36:38Z)

Other things:

  • The reorganisation is presumably to help people find the right framework - things like simple CGI-based APIs might not be cutting edge stuff, but they're potentially very useful if you don't have a "full" hosting account.
  • I didn't really agree with some aspects of the revised classifications. I think the template systems need their own page, and the multiple classifications really need banishing to another page where they'll confuse only the experts.

-- PaulBoddie

I'm afraid we need more fine-grained classification. It is unclear which of these components can be used together with others (say: is [http://www.chrisarndt.de/en/software/python/#auth Auth modules] compatible with CGI or mod_python?

-- Michal J. Gajda

If you want web programming to be more accessible, maybe you should avoid titles like "Variable Insertion-Replacement Templating Applications"?

-- FredrikLundh

I would expect Wiki technology to be included here. Seems ironic that MoinMoin is not mentioned on this page! (Other than here ... ;)

-- StephenWaterbury.

WebProgramming (last edited 2008-11-15 13:59:44 by localhost)

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