Merge pull request #480 from ppaez/typos
Typos
| | |
| | | |
| | | In the above example we've issued a call to |
| | | :meth:`~pyramid.config.Configurator.commit` between the two ``add_view`` |
| | | calls. :meth:`~pyramid.config.Configurator.commit` will cause any pending |
| | | calls. :meth:`~pyramid.config.Configurator.commit` will execute any pending |
| | | configuration statements. |
| | | |
| | | Calling :meth:`~pyramid.config.Configurator.commit` is safe at any time. It |
| | |
| | | When this view callable is called by Pyramid, the ``{'a':1}`` dictionary will |
| | | be rendered to a response on your behalf. The string passed as ``renderer=`` |
| | | above is an :term:`asset specification`. It is in the form |
| | | ``packagename:directoryname/filename.ext``. In this case, it names the |
| | | ``packagename:directoryname/filename.ext``. In this case, it refers to the |
| | | ``mytemplate.pt`` file in the ``templates`` directory within the ``myapp`` |
| | | Python package. Asset specifications are omnipresent in Pyramid: see |
| | | :ref:`intro_asset_specs` for more information. |