Home > Articles > Open Source > Python

An Introduction to Python Web Development Using the Pyramid Framework, Part 4

In Part 4 of his seven-part series on learning Python Pyramid, Jesse Smith examines the startup and request processes.
Like this article? We recommend

If you haven't read Part 3 of this series, I recommend you do that before continuing with this article. In Part 3, we looked at the project structure and what it means to an application.

This article covers the startup process , configuration files, and request processing. By taking a closer look at the application startup process, we can learn more about the configuration files as well. The request process is an artifact created by the startup process for handling user requests.

To get started, we'll first examine the startup process, which can be outlined in several steps that the pserve.exe command (Python server) takes to initialize an application.

Catch Up on All of the Articles in this Python Series

Jesse Smith has written four articles in this series. Here are the earlier installments:

Part 1
Part 3
Part 2

Startup Process

Figure 1 shows a simple workflow diagram of the system startup process.

The process begins by issuing a pserve.exe command from the command line:

pserver.exe \myproject development.ini –reload

pserve uses a library called PasteDeploy to create Web Server Gateway Interface (WSGI) application instances.

The first thing pserve.exe does is look at the information in the development.ini file. Next, pserve finds the main (that is, app:main) sections in the file. The most common applications use the [app:main] section to define the application's entry point. The entry point will be defined in this section's use= property. A sample [app:main] section is shown below:


use = egg:MyProject

pyramid.reload_templates = true
pyramid.debug_authorization = false
pyramid.debug_notfound = false
pyramid.debug_routematch = false
pyramid.default_locale_name = en
pyramid.includes =

In this example, the value egg:MyProject tells the paste.app_factory method (used by pserve) that the starting point of the application will be in a project named MyProject.

Next, pserve configures logging for the application defined by the [loggers], [loggers:root], and [logger:<project_name>] sections of the .ini file. An example of these three sections appears below:


keys = root, myproject

level = INFO
handlers = console

level = DEBUG
handlers =
qualname = myproject

Next, the __init__.py file is located, and a dictionary of key/value pairs from sections in the development.ini file are passed into the main function. For example:

def main(global_config, **settings):

    config = Configurator(settings=settings)
    config.add_static_view('static', 'static', cache_max_age=3600)
    config.add_route('home', '/')
    return config.make_wsgi_app()

Part 2 of this series covered the __init_.py file. The global_config parameter is a set of dictionary values that are obtained from the [DEFAULT] section (if it exists) of the development.ini file. The **settings parameter is a dictionary of the other settings needed to return a WSGI application instance provided by the [app:main] section.

A Configurator instance is created next, which creates the application's registry containing the configuration information.

Next, the config.make_wsgi_app() function returns a router instance that's used to connect the application server to the web server, thus creating the WSGI application instance.

Finally, the WSGI instance is returned to pserve, which calls the make_server method (not shown here) in the application's __init__.py file.

The server is now ready to serve requests.

Request Processing

Request processing details the lifecycle of a request to the application. From a high-level overview, this process is a basic one, as shown in the following steps to handle a request:

  1. A request is made from the browser to the server and port number defined in the application's __init__.py file.
  2. The router instance creates a request object by mapping the request URL to URL patterns provided by the route mapper.
  3. If a routing match is found, the request is passed into a view_callable matching the route.<
  4. The view_callable returns a response object that provides the response to the user. It could be simple text, custom text, or a template page.

The process of matching a route to a view is referred to as URL dispatching, which is discussed in the next section.

URL Dispatching

URL dispatching is actually part of the request-processing lifecycle, but should be explored further so you'll understand how Python associates a request to a view.

Typically, a Pyramid application will have a routing configuration. This configuration provides an ordered set of URLs that the application will use to map a request to a view. The code to achieve this goal is similar to the block of code below:

from views import myview

config.add_route('myroute', '/register/')
config.add_view(myview, route_name='myroute')

This code uses the add_route method to give the route a name. The add_view method associates that route to a view; However, the add_view method may be replaced with the scan method if you're using a Declarative Configuration (discussed in Part 2 of this series). The second parameter to the add_view method is the pattern. Of course, this can be more complicated than in the code example. For example, you could use replacement markers:

config.add_route('myroute', '/books/{id}')

The {id} segment in the pattern will accept any numbers or letters as a substitute.


In this article, you learned about the application startup, request, and URL dispatching processes. The startup process is mainly concerned with initializing the application and getting it ready to handle requests. The request process is the lifecycle of a request from a user to the application, which ends in a response. The URL dispatching process helps to fulfill the request process by matching the incoming URL to a view.

The development.ini file has several sections with settings that are used by the application startup process. These settings also include turning on debugging options; whereas, with the production.ini file, these options are disabled.

After learning about these core processing units, the next logical step is to move into the last part of the presentation layer of a Pyramid application, which is working with views. Part 5 of this series covers view concepts in more detail.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020