Follow the steps in :ref:`installing_chapter`, but name the virtualenv
directory pyramidtut
.
Switch to the
pyramidtut
directory:$ cd pyramidtut
Install tutorial dependencies:
$ $VENV/bin/easy_install docutils pyramid_tm pyramid_zodbconn \ pyramid_debugtoolbar nose coverage
Switch to the
pyramidtut
directory:c:\> cd pyramidtut
Install tutorial dependencies:
c:\pyramidtut> %VENV%\Scripts\easy_install docutils pyramid_tm \ pyramid_zodbconn pyramid_debugtoolbar nose coverage
Your next step is to create a project. For this tutorial, we will use the
:term:`scaffold` named zodb
, which generates an application
that uses :term:`ZODB` and :term:`traversal`. :app:`Pyramid`
supplies a variety of scaffolds to generate sample projects.
The below instructions assume your current working directory is the "virtualenv" named "pyramidtut".
On UNIX:
$ $VENV/bin/pcreate -s zodb tutorial
On Windows:
c:\pyramidtut> %VENV%\Scripts\pcreate -s zodb tutorial
Note
You don't have to call it tutorial -- the code uses relative paths for imports and finding templates and static resources.
Note
If you are using Windows, the zodb
scaffold
doesn't currently deal gracefully with installation into a location
that contains spaces in the path. If you experience startup
problems, try putting both the virtualenv and the project into
directories that do not contain spaces in their paths.
In order to do development on the project easily, you must "register"
the project as a development egg in your workspace using the
setup.py develop
command. In order to do so, cd to the "tutorial"
directory you created in :ref:`making_a_project`, and run the
"setup.py develop" command using virtualenv Python interpreter.
On UNIX:
$ cd tutorial
$ $VENV/bin/python setup.py develop
On Windows:
C:\pyramidtut> cd tutorial
C:\pyramidtut\tutorial> %VENV%\Scripts\python setup.py develop
After you've installed the project in development mode, you may run the tests for the project.
On UNIX:
$ $VENV/bin/python setup.py test -q
On Windows:
c:\pyramidtut\tutorial> %VENV%\Scripts\python setup.py test -q
You can run the nosetests
command to see test coverage
information. This runs the tests in the same way that setup.py
test
does but provides additional "coverage" information, exposing
which lines of your project are "covered" (or not covered) by the
tests.
On UNIX:
$ $VENV/bin/nosetests --cover-package=tutorial --cover-erase --with-coverage
On Windows:
c:\pyramidtut\tutorial> %VENV%\Scripts\nosetests --cover-package=tutorial ^
--cover-erase --with-coverage
Looks like the code in the zodb
scaffold for ZODB projects is
missing some test coverage, particularly in the file named
models.py
.
Start the application.
On UNIX:
$ $VENV/bin/pserve development.ini --reload
On Windows:
c:\pyramidtut\tutorial> %VENV%\Scripts\pserve development.ini --reload
Note
Your OS firewall, if any, may pop up a dialog asking for authorization to allow python to accept incoming network connections.
In a browser, visit http://localhost:6543/. You will see the generated application's default page.
One thing you'll notice is the "debug toolbar" icon on right hand side of the page. You can read more about the purpose of the icon at :ref:`debug_toolbar`. It allows you to get information about your application while you develop.
Creating a project using the zodb
scaffold makes the following
assumptions:
- you are willing to use :term:`ZODB` as persistent storage
- you are willing to use :term:`traversal` to map URLs to code.
Note
:app:`Pyramid` supports any persistent storage mechanism (e.g., a SQL database or filesystem files). :app:`Pyramid` also supports an additional mechanism to map URLs to code (:term:`URL dispatch`). However, for the purposes of this tutorial, we'll only be using traversal and ZODB.