summaryrefslogtreecommitdiff
path: root/docs/designdefense.rst
diff options
context:
space:
mode:
authorTshepang Lekhonkhobe <tshepang@gmail.com>2013-03-22 17:24:32 +0200
committerTshepang Lekhonkhobe <tshepang@gmail.com>2013-03-22 17:24:32 +0200
commit1ad8de2b9032b5a452b75274b8f908645c732e57 (patch)
tree334a567fd6e85c65790f970a59d2ca7661b902f9 /docs/designdefense.rst
parentcb93ae658624458032270c038070be8a20e33003 (diff)
downloadpyramid-1ad8de2b9032b5a452b75274b8f908645c732e57.tar.gz
pyramid-1ad8de2b9032b5a452b75274b8f908645c732e57.tar.bz2
pyramid-1ad8de2b9032b5a452b75274b8f908645c732e57.zip
remove unused ignore-next-block directive
Diffstat (limited to 'docs/designdefense.rst')
-rw-r--r--docs/designdefense.rst3
1 files changed, 0 insertions, 3 deletions
diff --git a/docs/designdefense.rst b/docs/designdefense.rst
index 749c9b099..7bc37ac06 100644
--- a/docs/designdefense.rst
+++ b/docs/designdefense.rst
@@ -120,7 +120,6 @@ that uses the ZCA global API is somewhat high. Consider a ZCA neophyte
reading the code that performs a typical "unnamed utility" lookup using the
:func:`zope.component.getUtility` global API:
-.. ignore-next-block
.. code-block:: python
:linenos:
@@ -190,7 +189,6 @@ special-purpose API functions that *do* use ZCA APIs. Take for example the
present in the current request or ``None`` if no userid is present in the
current request. The application developer calls it like so:
-.. ignore-next-block
.. code-block:: python
:linenos:
@@ -500,7 +498,6 @@ which match information in an associated "urlconf" such as
Zope, likewise allows you to add arbitrary keyword and positional
arguments to any method of a resource object found via traversal:
-.. ignore-next-block
.. code-block:: python
:linenos: