stackforge/pecan
Code Issues Proposed changes

Rearrange quickstart verbiage so users don't miss a necessary step.

Browse Source
This commit is contained in:
Ryan Petrello
2013-04-24 21:10:23 -04:00
parent 2813782d16
commit 475bade620
1 changed files with 6 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
docs/source/quick_start.rst
View File

@@ -22,13 +22,17 @@ your shell, type::
This example uses *test_project* as your project name, but you can replace
it with any valid Python package name you like.
Go ahead and change into your newly created project directory::
Go ahead and change into your newly created project directory. You'll want to
deploy it in "development mode", such that it’s available on ``sys.path``, yet
can still be edited directly from its source distribution::
$ cd test_project
$ ls
$ python setup.py develop
This is how the layout of your new project should look::
$ ls
├── MANIFEST.in
├── config.py
├── public
@@ -92,12 +96,6 @@ You may notice that **model/__init__.py** is mostly empty. If your project
will interact with a database, this if where you should add code to parse
bindings from your configuration file and define tables and ORM definitions.
Now that you've created your first Pecan application, you'll want to deploy it
in "development mode", such that it’s available on ``sys.path``, yet can still
be edited directly from its source distribution::
$ python setup.py develop
.. _running_application:
Running the Application