Файл: pyramid.pdf

20.2. THE INTERACTIVE SHELL

By defining the setup callable, we will create the module myapp.lib.pshell containing a callable named setup that will receive the global environment before it is exposed to the shell. Here we mutate the environment’s request as well as add a new value containing a WebTest version of the application to which we can easily submit requests.

6env[’request’].scheme = ’https’

7env[’testapp’] = TestApp(env[’app’])

When this INI file is loaded, the extra variables m, session and t will be available for use immediately. Since a setup callable was also specified, it is executed and a new variable testapp is exposed, and the request is configured to generate urls from the host http://www.example.com. For example:

chrism@thinko env26]$ bin/pshell starter/development.ini Python 2.6.5 (r265:79063, Apr 29 2010, 00:31:32)

[GCC 4.4.3] on linux2

Type "help" for more information.

Custom Variables:

mmyapp.models

session myapp.models.DBSession

ttransaction

>>> testapp.get(’/’)

<200 OK text/html body=’<!DOCTYPE...l>\n’/3337>

215

20.COMMAND-LINE PYRAMID

>>>request.route_url(’home’) ’https://www.example.com/’

20.2.2 IPython or bpython

If you have IPython or bpython or both installed in the interpreter you use to invoke the pshell command, pshell will autodiscover them and use the first respectively found in this order : IPython, bpython, standard Python interpreter. However you could specifically invoke one of your choice with the -p choice or --python-shell choice option.

[chrism@vitaminf shellenv]$ ../bin/pshell -p ipython | bpython | python \ development.ini#MyProject

20.3 Displaying All Application Routes

You can use the proutes command in a terminal window to print a summary of routes related to your application. Much like the pshell command (see The Interactive Shell), the proutes command accepts one argument with the format config_file#section_name. The config_file is the path to your application’s .ini file, and section_name is the app section name inside the .ini file which points to your application. By default, the section_name is main and can be omitted.

For example:

proutes generates a table. The table has three columns: a Name column, a Pattern column, and a View column. The items listed in the Name column are route names, the items listed in the Pattern column are route patterns, and the items listed in the View column are representations of the view callable that will be invoked when a request matches the associated route pattern. The view column may show None if no associated view callable could be found. If no routes are configured within your application, nothing will be printed to the console when proutes is executed.

216

20.4. DISPLAYING “TWEENS”

20.4 Displaying “Tweens”

A tween is a bit of code that sits between the main Pyramid application request handler and the WSGI application which calls it. A user can get a representation of both the implicit tween ordering (the ordering specified by calls to pyramid.config.Configurator.add_tween()) and the explicit tween ordering (specified by the pyramid.tweens configuration setting) orderings using the ptweens command. Tween factories will show up represented by their standard Python dotted name in the ptweens output.

For example, here’s the pwteens command run against a system configured without any explicit tweens:

Here’s the pwteens command run against a system configured with explicit tweens defined in its development.ini file:

217

20. COMMAND-LINE PYRAMID

Here’s the application configuration section of the development.ini used by the above ptweens command which reports that the explicit tween chain is used:

See Registering “Tweens” for more information about tweens.

20.5 Invoking a Request

You can use the prequest command-line utility to send a request to your application and see the response body without starting a server.

There are two required arguments to prequest:

•The config file/section: follows the format config_file#section_name where config_file is the path to your application’s .ini file and section_name is the app section name inside the .ini file. The section_name is optional, it defaults to main. For example: development.ini.

•The path: this should be the non-url-quoted path element of the URL to the resource you’d like to be rendered on the server. For example, /.

For example:

218