From 1ad8de2b9032b5a452b75274b8f908645c732e57 Mon Sep 17 00:00:00 2001 From: Tshepang Lekhonkhobe Date: Fri, 22 Mar 2013 17:24:32 +0200 Subject: remove unused ignore-next-block directive --- docs/designdefense.rst | 3 --- 1 file changed, 3 deletions(-) (limited to 'docs/designdefense.rst') 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: -- cgit v1.2.3