docs/quick_tutorial/debugtoolbar.rst | ●●●●● patch | view | raw | blame | history | |
docs/quick_tutorial/ini.rst | ●●●●● patch | view | raw | blame | history | |
docs/quick_tutorial/package.rst | ●●●●● patch | view | raw | blame | history |
docs/quick_tutorial/debugtoolbar.rst
@@ -74,11 +74,11 @@ you may click to provide introspective access to debugging information in a new browser tab. Even better, if your web application generates an error, you will see a nice traceback on the screen. When you want to disable this toolbar, no need to change code: you can remove it from ``pyramid.includes`` in the relevant ``.ini`` configuration file (thus showing why configuration files are handy.) toolbar, there's no need to change code: you can remove it from ``pyramid.includes`` in the relevant ``.ini`` configuration file (thus showing why configuration files are handy.) Note that the toolbar injects a small amount of html/css into your app just Note that the toolbar injects a small amount of HTML/CSS into your app just before the closing ``</body>`` tag in order to display itself. If you start to experience otherwise inexplicable client-side weirdness, you can shut it off by commenting out the ``pyramid_debugtoolbar`` line in ``pyramid.includes`` docs/quick_tutorial/ini.rst
@@ -88,7 +88,7 @@ - ``pserve`` looks for ``[app:main]`` and finds ``use = egg:tutorial`` - The projects's ``setup.py`` has defined an "entry point" (lines 9-10) - The projects's ``setup.py`` has defined an "entry point" (lines 9-12) for the project "main" entry point of ``tutorial:main`` - The ``tutorial`` package's ``__init__`` has a ``main`` function docs/quick_tutorial/package.rst
@@ -3,7 +3,7 @@ ============================================ Most modern Python development is done using Python packages, an approach Pyramid puts to good use. In this step we re-do "Hello World" as a Pyramid puts to good use. In this step we redo "Hello World" as a minimum Python package inside a minimum Python project. Background @@ -93,7 +93,7 @@ our package is installed (in this case, in local development mode.) In this step we have a Python package called ``tutorial``. We use the same name in each step of the tutorial, to avoid unnecessary re-typing. same name in each step of the tutorial, to avoid unnecessary retyping. Above this ``tutorial`` directory we have the files that handle the packaging of this project. At the moment, all we need is a