cherrypy.test.modpy module

Wrapper for mod_python, for use as a CherryPy HTTP server when testing.

To autostart modpython, the “apache” executable or script must be on your system path, or you must override the global APACHE_PATH. On some platforms, “apache” may be called “apachectl” or “apache2ctl”– create a symlink to them if needed.

If you wish to test the WSGI interface instead of our _cpmodpy interface, you also need the ‘modpython_gateway’ module at:


  1. Apache processes Range headers automatically; CherryPy’s truncated

    output is then truncated again by Apache. See test_core.testRanges. This was worked around in

  2. Apache does not allow custom HTTP methods like CONNECT as per the spec.

    See test_core.testHTTPMethods.

  3. Max request header and body settings do not work with Apache.

  4. Apache replaces status “reason phrases” automatically. For example,

    CherryPy may set “304 Not modified” but Apache will write out “304 Not Modified” (capital “M”).

  5. Apache does not allow custom error codes as per the spec.

  6. Apache (or perhaps modpython, or modpython_gateway) unquotes %xx in the

    Request-URI too early.

  7. mod_python will not read request bodies which use the “chunked”

    transfer-coding (it passes REQUEST_CHUNKED_ERROR to ap_setup_client_block instead of REQUEST_CHUNKED_DECHUNK, see Apache2’s http_protocol.c and mod_python’s requestobject.c).

  8. Apache will output a “Content-Length: 0” response header even if there’s

    no response entity body. This isn’t really a bug; it just differs from the CherryPy default.

class cherrypy.test.modpy.ModPythonSupervisor(**kwargs)[source]

Bases: cherrypy.test.helper.Supervisor


Gracefully shutdown a server that is serving forever.

template = None
using_apache = True
using_wsgi = False
cherrypy.test.modpy.read_process(cmd, args='')[source]