Command-Line Pyramid¶
Your Pyramid application can be controlled and inspected using a variety of command-line utilities. These utilities are documented in this chapter.
Displaying Matching Views for a Given URL¶
For a big application with several views, it can be hard to keep the view
configuration details in your head, even if you defined all the views
yourself. You can use the paster pviews
command in a terminal window to
print a summary of matching routes and views for a given URL in your
application. The paster pviews
command accepts two arguments. The first
argument to pviews
is the path to your application’s .ini
file and
section name inside the .ini
file which points to your application. This
should be of the format config_file#section_name
. The second argument is
the URL to test for matching views. The section_name
may be omitted; if
it is, it’s considered to be main
.
Here is an example for a simple view configuration using traversal:
1 2 3 4 5 6 7 8 9 10 11 | $ ../bin/paster pviews development.ini#tutorial /FrontPage
URL = /FrontPage
context: <tutorial.models.Page object at 0xa12536c>
view name:
View:
-----
tutorial.views.view_page
required permission = view
|
The output always has the requested URL at the top and below that all the views that matched with their view configuration details. In this example only one view matches, so there is just a single View section. For each matching view, the full code path to the associated view callable is shown, along with any permissions and predicates that are part of that view configuration.
A more complex configuration might generate something like this:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 | $ ../bin/paster pviews development.ini#shootout /about
URL = /about
context: <shootout.models.RootFactory object at 0xa56668c>
view name: about
Route:
------
route name: about
route pattern: /about
route path: /about
subpath:
route predicates (request method = GET)
View:
-----
shootout.views.about_view
required permission = view
view predicates (request_param testing, header X/header)
Route:
------
route name: about_post
route pattern: /about
route path: /about
subpath:
route predicates (request method = POST)
View:
-----
shootout.views.about_view_post
required permission = view
view predicates (request_param test)
View:
-----
shootout.views.about_view_post2
required permission = view
view predicates (request_param test2)
|
In this case, we are dealing with a URL dispatch application. This specific URL has two matching routes. The matching route information is displayed first, followed by any views that are associated with that route. As you can see from the second matching route output, a route can be associated with more than one view.
For a URL that doesn’t match any views, paster pviews
will simply print
out a Not found message.
The Interactive Shell¶
Once you’ve installed your program for development using setup.py
develop
, you can use an interactive Python shell to execute expressions in
a Python environment exactly like the one that will be used when your
application runs “for real”. To do so, use the paster pshell
command.
The argument to pshell
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 which
points to your application. For example, if your application .ini
file
might have a [app:MyProject]
section that looks like so:
1 2 3 4 5 6 7 | [app:MyProject]
use = egg:MyProject
reload_templates = true
debug_authorization = false
debug_notfound = false
debug_templates = true
default_locale_name = en
|
If so, you can use the following command to invoke a debug shell using the
name MyProject
as a section name:
chrism@thinko env26]$ bin/paster pshell starter/development.ini#MyProject
Python 2.6.5 (r265:79063, Apr 29 2010, 00:31:32)
[GCC 4.4.3] on linux2
Type "help" for more information.
Environment:
app The WSGI application.
registry Active Pyramid registry.
request Active request object.
root Root of the default resource tree.
root_factory Default root factory used to create `root`.
>>> root
<myproject.resources.MyResource object at 0x445270>
>>> registry
<Registry myproject>
>>> registry.settings['debug_notfound']
False
>>> from myproject.views import my_view
>>> from pyramid.request import Request
>>> r = Request.blank('/')
>>> my_view(r)
{'project': 'myproject'}
The WSGI application that is loaded will be available in the shell as the
app
global. Also, if the application that is loaded is the Pyramid
app with no surrounding middleware, the root
object returned by the
default root factory, registry
, and request
will be
available.
You can also simply rely on the main
default section name by omitting any
hash after the filename:
chrism@thinko env26]$ bin/paster pshell starter/development.ini
Press Ctrl-D
to exit the interactive shell (or Ctrl-Z
on Windows).
Extending the Shell¶
It is sometimes convenient when using the interactive shell often to have
some variables significant to your application already loaded as globals when
you start the pshell
. To facilitate this, pshell
will look for a
special [pshell]
section in your INI file and expose the subsequent
key/value pairs to the shell. Each key is a variable name that will be
global within the pshell session; each value is a dotted Python name.
For example, you want to expose your model to the shell, along with the
database session so that you can mutate the model on an actual database.
Here, we’ll assume your model is stored in the myapp.models
package.
1 2 3 4 | [pshell]
m = myapp.models
session = myapp.models.DBSession
t = transaction
|
When this INI file is loaded, the extra variables m
, session
and
t
will be available for use immediately. For example:
chrism@thinko env26]$ bin/paster 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.
Environment:
app The WSGI application.
registry Active Pyramid registry.
request Active request object.
root Root of the default resource tree.
root_factory Default root factory used to create `root`.
Custom Variables:
m myapp.models
session myapp.models.DBSession
t transaction
>>>
IPython¶
If you have IPython installed in
the interpreter you use to invoke the paster
command, the pshell
command will use an IPython interactive shell instead of a standard Python
interpreter shell. If you don’t want this to happen, even if you have
IPython installed, you can pass the --disable-ipython
flag to the
pshell
command to use a standard Python interpreter shell
unconditionally.
[chrism@vitaminf shellenv]$ ../bin/paster pshell --disable-ipython \
development.ini#MyProject
Displaying All Application Routes¶
You can use the paster proutes
command in a terminal window to print a
summary of routes related to your application. Much like the paster
pshell
command (see The Interactive Shell), the paster 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:
1 2 3 4 5 6 7 8 | [chrism@thinko MyProject]$ ../bin/paster proutes development.ini#MyProject
Name Pattern View
---- ------- ----
home / <function my_view>
home2 / <function my_view>
another /another None
static/ static/*subpath <static_view object>
catchall /*subpath <function static_view>
|
paster 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 paster proutes
is executed.
Writing a Script¶
All web applications are, at their hearts, systems which accept a request and
return a response. When a request is accepted by a Pyramid
application, the system receives state from the request which is later relied
on by your application code. For example, one view callable may assume
it’s working against a request that has a request.matchdict
of a
particular composition, while another assumes a different composition of the
matchdict.
In the meantime, it’s convenient to be able to write a Python script that can work “in a Pyramid environment”, for instance to update database tables used by your Pyramid application. But a “real” Pyramid environment doesn’t have a completely static state independent of a request; your application (and Pyramid itself) is almost always reliant on being able to obtain information from a request. When you run a Python script that simply imports code from your application and tries to run it, there just is no request data, because there isn’t any real web request. Therefore some parts of your application and some Pyramid APIs will not work.
For this reason, Pyramid makes it possible to run a script in an
environment much like the environment produced when a particular
request reaches your Pyramid application. This is achieved by
using the pyramid.paster.bootstrap()
command in the body of your
script.
Note
This feature is new as of Pyramid 1.1.
In the simplest case, pyramid.paster.bootstrap()
can be used with a
single argument, which accepts the PasteDeploy .ini
file
representing Pyramid your application configuration as a single argument:
from pyramid.paster import bootstrap
env = bootstrap('/path/to/my/development.ini')
print env['request'].route_url('home')
pyramid.paster.bootstrap()
returns a dictionary containing
framework-related information. This dictionary will always contain a
request object as its request
key.
The following keys are available in the env
dictionary returned by
pyramid.paster.bootstrap()
:
request
Apyramid.request.Request
object implying the current request state for your script.
app
The WSGI application object generated by bootstrapping.
root
The resource root of your Pyramid application. This is an object generated by the root factory configured in your application.
registry
The application registry of your Pyramid application.
closer
A parameterless callable that can be used to pop an internal Pyramid threadlocal stack (used bypyramid.threadlocal.get_current_registry()
andpyramid.threadlocal.get_current_request()
) when your scripting job is finished.
Let’s assume that the /path/to/my/development.ini
file used in the
example above looks like so:
[pipeline:main]
pipeline = egg:WebError#evalerror
another
[app:another]
use = egg:MyProject
The configuration loaded by the above bootstrap example will use the
configuration implied by the [pipeline:main]
section of your
configuration file by default. Specifying /path/to/my/development.ini
is
logically equivalent to specifying /path/to/my/development.ini#main
. In
this case, we’ll be using a configuration that includes an app
object
which is wrapped in the WebError evalerror
middleware.
You can also specify a particular section of the PasteDeploy .ini
file
to load instead of main
:
from pyramid.paster import bootstrap
env = bootstrap('/path/to/my/development.ini#another')
print env['request'].route_url('home')
The above example specifies the another
app
, pipeline
, or
composite
section of your PasteDeploy configuration file. The app
object present in the env
dictionary returned by
pyramid.paster.bootstrap()
will be a Pyramid router.
Changing the Request¶
By default, Pyramid will generate a request object in the env
dictionary
for the URL http://localhost:80/
. This means that any URLs generated
by Pyramid during the execution of your script will be anchored here. This
is generally not what you want.
So how do we make Pyramid generate the correct URLs?
Assuming that you have a route configured in your application like so:
config.add_route('verify', '/verify/{code}')
You need to inform the Pyramid environment that the WSGI application is handling requests from a certain base. For example, we want to mount our application at example.com/prefix and the generated URLs should use HTTPS. This can be done by mutating the request object:
from pyramid.paster import bootstrap
env = bootstrap('/path/to/my/development.ini#another')
env['request'].host = 'example.com'
env['request'].scheme = 'https'
env['request'].script_name = '/prefix'
print env['request'].application_url
# will print 'https://example.com/prefix/another/url'
Now you can readily use Pyramid’s APIs for generating URLs:
route_url('verify', env['request'], code='1337')
# will return 'https://example.com/prefix/verify/1337'
Cleanup¶
When your scripting logic finishes, it’s good manners (but not required) to
call the closer
callback:
from pyramid.paster import bootstrap
env = bootstrap('/path/to/my/development.ini')
# .. do stuff ...
env['closer']()
Setting Up Logging¶
By default, pyramid.paster.bootstrap()
does not configure logging
parameters present in the configuration file. If you’d like to configure
logging based on [logger]
and related sections in the configuration file,
use the following command:
import logging
logging.fileConfig('/path/to/my/development.ini')