diff options
| author | Steve Piercy <web@stevepiercy.com> | 2016-03-02 22:57:48 -0800 |
|---|---|---|
| committer | Steve Piercy <web@stevepiercy.com> | 2016-03-02 22:58:23 -0800 |
| commit | 6c36d783bf6d3a289afe559d6595d96de3d99d89 (patch) | |
| tree | 67a1cac8c545c2d122aca6bb16c3b8e3a0e77801 /docs/designdefense.rst | |
| parent | 74675f77aa96e82c228861d7339ff639fb7f243c (diff) | |
| download | pyramid-6c36d783bf6d3a289afe559d6595d96de3d99d89.tar.gz pyramid-6c36d783bf6d3a289afe559d6595d96de3d99d89.tar.bz2 pyramid-6c36d783bf6d3a289afe559d6595d96de3d99d89.zip | |
update link to videos
Diffstat (limited to 'docs/designdefense.rst')
| -rw-r--r-- | docs/designdefense.rst | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/designdefense.rst b/docs/designdefense.rst index 28da84368..5f3295305 100644 --- a/docs/designdefense.rst +++ b/docs/designdefense.rst @@ -1011,8 +1011,8 @@ Self-described "microframeworks" exist. `Bottle <http://bottle.paws.de>`_ and <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. @@ -1542,7 +1542,7 @@ inlined comments take into account what we've discussed in the 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 @@ -1550,7 +1550,7 @@ configuration using :meth:`~pyramid.config.Configurator.include`. Any 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 |