From Wikipedia, the free encyclopedia
Jump to: navigation, search
Developer(s) CherryPy team
Stable release 4.0.0[1] / December 20, 2015; 55 days ago (2015-12-20)
Written in Python
Operating system Cross-platform
Type Web application framework
License BSD License[2]

CherryPy is an object-oriented web application framework using the Python programming language. It is designed for rapid development of web applications by wrapping the HTTP protocol but stays at a low level and does not offer much more than what is defined in RFC 7231.

CherryPy can be a web server itself or one can launch it via any WSGI compatible environment. It does not deal with tasks such as templating for output rendering or backend access. The framework is extensible with filters, which are called at defined points in the request/response processing.

Pythonic interface[edit]

One of the goals of the project founder, Remi Delon, was to make CherryPy as pythonic as possible. This allows the developer to use the framework as any regular Python module and to forget (from a technical point of view) that the application is for the web.

For instance, the common Hello World program with CherryPy 3 would look like:

import cherrypy

class HelloWorld(object):
    def index(self):
        return "Hello World!" = True



CherryPy implements:

  • A HTTP/1.1-compliant, WSGI thread-pooled webserver.[3] Typically, CherryPy itself takes only 1-2 ms per page.[4][5]
  • Support for any other WSGI-enabled web server or adapter, including Apache, IIS, lighttpd, mod_python, FastCGI, SCGI, and mod_wsgi.
  • A native mod_python adapter.
  • Multiple HTTP servers (e.g. ability to listen on multiple ports).[6]
  • A plugin system[7] CherryPy plugins hook into events within the server process — into server startup, server shutdown, server exiting, etc. — to run code that needs to be run when the server starts up or shuts down.
  • Built-in tools for caching, encoding, sessions, authorization, static content, and others. CherryPy tools hook into events within the request process. Whenever the CherryPy server receives a request, there is a specific set of steps it goes through to handle that request. Page handlers are only one step in the process. Tools also provide a syntax and configuration API for turning them on and off for a specific set of handlers.
  • A configuration system for developers and deployers .[8][9][10] CherryPy deployments are configurable on site, on application and on controller level, through Python dictionaries, configuration files, and open file objects.
  • A complete test suite for core functionality and associated framework which can be used to test CherryPy applications.[11]
  • Built-in profiling since v2.1,[12] coverage[13] and testing support.

CherryPy doesn’t force you to use a specific object-relational mapper (ORM), template language or JavaScript library.

Can be used with CherryPy[edit]

  • Routes[14] — a Python re-implementation of the Ruby on Rails's routes system for mapping URLs to controllers/actions and generating URLs.

Object-relational mappers[edit]

Templating languages[edit]

  • Mako[18] — a template library written in Python, usable with a simple CherryPy tool.[19]
  • Cheetah — an open source template engine and code generation tool, written in Python.
  • CherryTemplate — a templating language for CherryPy.
  • Genshi[20][21] — a powerful XML templating language.
  • Jinja — a general purpose templating language. CherryPy has a tool for using Jinja templates.[22]
  • Kid — a simple template language for XML based vocabularies written in Python. TurboGears 1.x uses CherryPy as server and Kid as frontend.[23]

CherryPy wiki helps[24] choosing a templating language.

JavaScript libraries[edit]

  • Sarissa[25] — a cross-browser library for Ajax
  • jQuery — a lightweight library that emphasizes interaction between JavaScript and HTML
  • Pyjamas — a Python to JavaScript compiler and a web widget set

Products using CherryPy[edit]


External links[edit]