04: Easier Development with
Error handling and introspection using the
As we introduce the basics, we also want to show how to be productive in
development and debugging. For example, we just discussed template reloading,
and earlier we showed
--reload for application reloading.
pyramid_debugtoolbar is a popular Pyramid add-on which makes several tools
available in your browser. Adding it to your project illustrates several points
- Install and enable the toolbar to help during development.
- Explain Pyramid add-ons.
- Show how an add-on gets configured into your application.
First we copy the results of the previous step, as well as install the
$ cd ..; cp -r ini debugtoolbar; cd debugtoolbar $ $VENV/bin/pip install -e . $ $VENV/bin/pip install pyramid_debugtoolbar
debugtoolbar/development.inigets a configuration entry for
1 2 3 4 5 6 7 8 9
[app:main] use = egg:tutorial pyramid.includes = pyramid_debugtoolbar [server:main] use = egg:pyramid#wsgiref host = 0.0.0.0 port = 6543
Run the WSGI application with:
$ $VENV/bin/pserve development.ini --reload
Open http://localhost:6543/ in your browser. See the handy toolbar on the right.
pyramid_debugtoolbar is a full-fledged Python package, available on PyPI
just like thousands of other Python packages. Thus we start by installing the
pyramid_debugtoolbar package into our virtual environment using normal
Python package installation commands.
pyramid_debugtoolbar Python package is also a Pyramid add-on, which
means we need to include its add-on configuration into our web application. We
could do this with imperative configuration in
config.include. Pyramid also supports wiring in add-on configuration
pyramid.includes. We use this to load the
configuration for the debugtoolbar.
You'll now see an attractive button on the right side of your browser, which
you may click to provide introspective access to debugging information in a new
rowser tab. Even better, if your web application generates an error, you will
see a nice traceback on the screen. When you want to disable this toolbar,
there's no need to change code: you can remove it from
.ini configuration file (thus showing why configuration files
Note that the toolbar injects a small amount of HTML/CSS into your app just
before the closing
</body> tag in order to display itself. If you start to
experience otherwise inexplicable client-side weirdness, you can shut it off
by commenting out the
pyramid_debugtoolbar line in
See also pyramid_debugtoolbar.
Why don't we add
pyramid_debugtoolbarto the list of
Introduce a bug into your application. Change:
def hello_world(request): return Response('<body><h1>Hello World!</h1></body>')
def hello_world(request): return xResponse('<body><h1>Hello World!</h1></body>')
Save, and visit http://localhost:6543/ again. Notice the nice traceback display. On the lowest line, click the "screen" icon to the right, and try typing the variable names
Response. What else can you discover?