docs/designdefense.rst | ●●●●● patch | view | raw | blame | history | |
docs/quick_tutorial/routing.rst | ●●●●● patch | view | raw | blame | history |
docs/designdefense.rst
@@ -1015,8 +1015,8 @@ <http://bobo.digicool.com/>`_ doesn't describe itself as a microframework, but its intended user base is much the same. Many others exist. We've even (only as a teaching tool, not as any sort of official project) `created one using Pyramid <http://bfg.repoze.org/videos#groundhog1>`_. The videos use BFG, a precursor to Pyramid, but the resulting code is `available for Pyramid too Pyramid <http://static.repoze.org/casts/videotags.html>`_. The videos use BFG, a precursor to Pyramid, but the resulting code is `available for Pyramid too <https://github.com/Pylons/groundhog>`_). Microframeworks are small frameworks with one common feature: each allows its users to create a fully functional application that lives in a single Python file. @@ -1546,7 +1546,7 @@ server.serve_forever() # explicitly WSGI Pyramid Doesn't Offer Pluggable Apps Pyramid doesn't offer pluggable apps ------------------------------------ It is "Pyramidic" to compose multiple external sources into the same @@ -1554,7 +1554,7 @@ number of includes can be done to compose an application; includes can even be done from within other includes. Any directive can be used within an include that can be used outside of one (such as :meth:`~pyramid.config.Configurator.add_view`, etc). :meth:`~pyramid.config.Configurator.add_view`). Pyramid has a conflict detection system that will throw an error if two included externals try to add the same configuration in a conflicting way docs/quick_tutorial/routing.rst
@@ -23,14 +23,14 @@ .. note:: Why do this twice? Other Python web frameworks let you create a route and associate it with a view in one step. As illustrated in :ref:`routes_need_ordering`, multiple routes might match the same URL pattern. Rather than provide ways to help guess, Pyramid lets you be explicit in ordering. Pyramid also gives facilities to avoid the problem. It's relatively easy to build a system that uses implicit route ordering with Pyramid too. See `The Groundhog series of screencasts <http://bfg.repoze.org/videos#groundhog1>`_ if you're interested in Why do this twice? Other Python web frameworks let you create a route and associate it with a view in one step. As illustrated in :ref:`routes_need_ordering`, multiple routes might match the same URL pattern. Rather than provide ways to help guess, Pyramid lets you be explicit in ordering. Pyramid also gives facilities to avoid the problem. It's relatively easy to build a system that uses implicit route ordering with Pyramid too. See `The Groundhog series of screencasts <http://static.repoze.org/casts/videotags.html>`_ if you're interested in doing so. Objectives