From 28f659844f0f3520a8bedf4d318970b039bf9734 Mon Sep 17 00:00:00 2001 From: Steve Piercy Date: Fri, 23 Nov 2018 18:42:18 -0800 Subject: Remove redundancy in appmaker narrative --- docs/tutorials/wiki/basiclayout.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'docs/tutorials/wiki') diff --git a/docs/tutorials/wiki/basiclayout.rst b/docs/tutorials/wiki/basiclayout.rst index 7e6e86143..39e15bb58 100644 --- a/docs/tutorials/wiki/basiclayout.rst +++ b/docs/tutorials/wiki/basiclayout.rst @@ -174,12 +174,12 @@ Here is the source for ``models.py``: #. *Lines 8-12*. ``appmaker`` is used to return the *application root* object. - It is called on *every request* to the :app:`Pyramid` application. + It is called on *every request* to the :app:`Pyramid` application by virtue of the ``root_factory`` defined in our ``__init__.py``. It also performs bootstrapping by *creating* an application root (inside the ZODB root object) if one does not already exist. - It is used by the ``root_factory`` we have defined in our ``__init__.py``. - + Bootstrapping is done by first seeing if the database has the persistent application root. If not, then we make an instance, store it, and commit the transaction. + We then return the application root object. -- cgit v1.2.3