From: Gregory P. Smith <greg@mad-scientist.com>
Date: Mon, 2 Mar 2009 04:53:24 +0000 (+0000)
Subject: The note about caching of regular expression objects was incorrect ReST and
X-Git-Tag: v2.7a1~1919
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=0261e5d0b65c6a935f88f59629ea658296cb3d8a;p=python

The note about caching of regular expression objects was incorrect ReST and
thus invisible in the compiled documentation.  Fixed.  Also I cleaned up the
wording.
---

diff --git a/Doc/library/re.rst b/Doc/library/re.rst
index 96b452ecc6..2237f070b9 100644
--- a/Doc/library/re.rst
+++ b/Doc/library/re.rst
@@ -440,19 +440,23 @@ form.
 
    The sequence ::
 
-      prog = re.compile(pat)
-      result = prog.match(str)
+      prog = re.compile(pattern)
+      result = prog.match(string)
 
    is equivalent to ::
 
-      result = re.match(pat, str)
+      result = re.match(pattern, string)
 
-   but the version using :func:`compile` is more efficient when the expression
-   will be used several times in a single program.
+   but using :func:`compile` and saving the resulting regular expression object
+   for reuse is more efficient when the expression will be used several times
+   in a single program.
 
-   .. (The compiled version of the last pattern passed to :func:`re.match` or
-      :func:`re.search` is cached, so programs that use only a single regular
-      expression at a time needn't worry about compiling regular expressions.)
+   .. note::
+
+      The compiled versions of the most recent patterns passed to
+      :func:`re.match`, :func:`re.search` or :func:`re.compile` are cached, so
+      programs that use only a few regular expressions at a time needn't worry
+      about compiling regular expressions.
 
 
 .. data:: I