blob: 2ab12546e9864fd716c49ee4ff44aefc27726e2d [file] [log] [blame]
Georg Brandl8ec7f652007-08-15 14:28:01 +00001
2:mod:`re` --- Regular expression operations
3===========================================
4
5.. module:: re
6 :synopsis: Regular expression operations.
7.. moduleauthor:: Fredrik Lundh <fredrik@pythonware.com>
8.. sectionauthor:: Andrew M. Kuchling <amk@amk.ca>
9
10
11
12
13This module provides regular expression matching operations similar to
14those found in Perl. Both patterns and strings to be searched can be
15Unicode strings as well as 8-bit strings. The :mod:`re` module is
16always available.
17
18Regular expressions use the backslash character (``'\'``) to indicate
19special forms or to allow special characters to be used without invoking
20their special meaning. This collides with Python's usage of the same
21character for the same purpose in string literals; for example, to match
22a literal backslash, one might have to write ``'\\\\'`` as the pattern
23string, because the regular expression must be ``\\``, and each
24backslash must be expressed as ``\\`` inside a regular Python string
25literal.
26
27The solution is to use Python's raw string notation for regular expression
28patterns; backslashes are not handled in any special way in a string literal
29prefixed with ``'r'``. So ``r"\n"`` is a two-character string containing
30``'\'`` and ``'n'``, while ``"\n"`` is a one-character string containing a
Georg Brandlba2e5192007-09-27 06:26:58 +000031newline. Usually patterns will be expressed in Python code using this raw
32string notation.
Georg Brandl8ec7f652007-08-15 14:28:01 +000033
Georg Brandlb8df1562007-12-05 18:30:48 +000034It is important to note that most regular expression operations are available as
35module-level functions and :class:`RegexObject` methods. The functions are
36shortcuts that don't require you to compile a regex object first, but miss some
37fine-tuning parameters.
38
Georg Brandl8ec7f652007-08-15 14:28:01 +000039.. seealso::
40
41 Mastering Regular Expressions
42 Book on regular expressions by Jeffrey Friedl, published by O'Reilly. The
Georg Brandlba2e5192007-09-27 06:26:58 +000043 second edition of the book no longer covers Python at all, but the first
Georg Brandl8ec7f652007-08-15 14:28:01 +000044 edition covered writing good regular expression patterns in great detail.
45
46
47.. _re-syntax:
48
49Regular Expression Syntax
50-------------------------
51
52A regular expression (or RE) specifies a set of strings that matches it; the
53functions in this module let you check if a particular string matches a given
54regular expression (or if a given regular expression matches a particular
55string, which comes down to the same thing).
56
57Regular expressions can be concatenated to form new regular expressions; if *A*
58and *B* are both regular expressions, then *AB* is also a regular expression.
59In general, if a string *p* matches *A* and another string *q* matches *B*, the
60string *pq* will match AB. This holds unless *A* or *B* contain low precedence
61operations; boundary conditions between *A* and *B*; or have numbered group
62references. Thus, complex expressions can easily be constructed from simpler
63primitive expressions like the ones described here. For details of the theory
64and implementation of regular expressions, consult the Friedl book referenced
65above, or almost any textbook about compiler construction.
66
67A brief explanation of the format of regular expressions follows. For further
Georg Brandl1cf05222008-02-05 12:01:24 +000068information and a gentler presentation, consult the :ref:`regex-howto`.
Georg Brandl8ec7f652007-08-15 14:28:01 +000069
70Regular expressions can contain both special and ordinary characters. Most
71ordinary characters, like ``'A'``, ``'a'``, or ``'0'``, are the simplest regular
72expressions; they simply match themselves. You can concatenate ordinary
73characters, so ``last`` matches the string ``'last'``. (In the rest of this
74section, we'll write RE's in ``this special style``, usually without quotes, and
75strings to be matched ``'in single quotes'``.)
76
77Some characters, like ``'|'`` or ``'('``, are special. Special
78characters either stand for classes of ordinary characters, or affect
79how the regular expressions around them are interpreted. Regular
80expression pattern strings may not contain null bytes, but can specify
81the null byte using the ``\number`` notation, e.g., ``'\x00'``.
82
83
84The special characters are:
85
Georg Brandl8ec7f652007-08-15 14:28:01 +000086``'.'``
87 (Dot.) In the default mode, this matches any character except a newline. If
88 the :const:`DOTALL` flag has been specified, this matches any character
89 including a newline.
90
91``'^'``
92 (Caret.) Matches the start of the string, and in :const:`MULTILINE` mode also
93 matches immediately after each newline.
94
95``'$'``
96 Matches the end of the string or just before the newline at the end of the
97 string, and in :const:`MULTILINE` mode also matches before a newline. ``foo``
98 matches both 'foo' and 'foobar', while the regular expression ``foo$`` matches
99 only 'foo'. More interestingly, searching for ``foo.$`` in ``'foo1\nfoo2\n'``
Amaury Forgeot d'Arcd08a8eb2008-01-10 21:59:42 +0000100 matches 'foo2' normally, but 'foo1' in :const:`MULTILINE` mode; searching for
101 a single ``$`` in ``'foo\n'`` will find two (empty) matches: one just before
102 the newline, and one at the end of the string.
Georg Brandl8ec7f652007-08-15 14:28:01 +0000103
104``'*'``
105 Causes the resulting RE to match 0 or more repetitions of the preceding RE, as
106 many repetitions as are possible. ``ab*`` will match 'a', 'ab', or 'a' followed
107 by any number of 'b's.
108
109``'+'``
110 Causes the resulting RE to match 1 or more repetitions of the preceding RE.
111 ``ab+`` will match 'a' followed by any non-zero number of 'b's; it will not
112 match just 'a'.
113
114``'?'``
115 Causes the resulting RE to match 0 or 1 repetitions of the preceding RE.
116 ``ab?`` will match either 'a' or 'ab'.
117
118``*?``, ``+?``, ``??``
119 The ``'*'``, ``'+'``, and ``'?'`` qualifiers are all :dfn:`greedy`; they match
120 as much text as possible. Sometimes this behaviour isn't desired; if the RE
121 ``<.*>`` is matched against ``'<H1>title</H1>'``, it will match the entire
122 string, and not just ``'<H1>'``. Adding ``'?'`` after the qualifier makes it
123 perform the match in :dfn:`non-greedy` or :dfn:`minimal` fashion; as *few*
124 characters as possible will be matched. Using ``.*?`` in the previous
125 expression will match only ``'<H1>'``.
126
127``{m}``
128 Specifies that exactly *m* copies of the previous RE should be matched; fewer
129 matches cause the entire RE not to match. For example, ``a{6}`` will match
130 exactly six ``'a'`` characters, but not five.
131
132``{m,n}``
133 Causes the resulting RE to match from *m* to *n* repetitions of the preceding
134 RE, attempting to match as many repetitions as possible. For example,
135 ``a{3,5}`` will match from 3 to 5 ``'a'`` characters. Omitting *m* specifies a
136 lower bound of zero, and omitting *n* specifies an infinite upper bound. As an
137 example, ``a{4,}b`` will match ``aaaab`` or a thousand ``'a'`` characters
138 followed by a ``b``, but not ``aaab``. The comma may not be omitted or the
139 modifier would be confused with the previously described form.
140
141``{m,n}?``
142 Causes the resulting RE to match from *m* to *n* repetitions of the preceding
143 RE, attempting to match as *few* repetitions as possible. This is the
144 non-greedy version of the previous qualifier. For example, on the
145 6-character string ``'aaaaaa'``, ``a{3,5}`` will match 5 ``'a'`` characters,
146 while ``a{3,5}?`` will only match 3 characters.
147
148``'\'``
149 Either escapes special characters (permitting you to match characters like
150 ``'*'``, ``'?'``, and so forth), or signals a special sequence; special
151 sequences are discussed below.
152
153 If you're not using a raw string to express the pattern, remember that Python
154 also uses the backslash as an escape sequence in string literals; if the escape
155 sequence isn't recognized by Python's parser, the backslash and subsequent
156 character are included in the resulting string. However, if Python would
157 recognize the resulting sequence, the backslash should be repeated twice. This
158 is complicated and hard to understand, so it's highly recommended that you use
159 raw strings for all but the simplest expressions.
160
161``[]``
162 Used to indicate a set of characters. Characters can be listed individually, or
163 a range of characters can be indicated by giving two characters and separating
164 them by a ``'-'``. Special characters are not active inside sets. For example,
165 ``[akm$]`` will match any of the characters ``'a'``, ``'k'``,
166 ``'m'``, or ``'$'``; ``[a-z]`` will match any lowercase letter, and
167 ``[a-zA-Z0-9]`` matches any letter or digit. Character classes such
168 as ``\w`` or ``\S`` (defined below) are also acceptable inside a
169 range, although the characters they match depends on whether :const:`LOCALE`
170 or :const:`UNICODE` mode is in force. If you want to include a
171 ``']'`` or a ``'-'`` inside a set, precede it with a backslash, or
172 place it as the first character. The pattern ``[]]`` will match
173 ``']'``, for example.
174
175 You can match the characters not within a range by :dfn:`complementing` the set.
176 This is indicated by including a ``'^'`` as the first character of the set;
177 ``'^'`` elsewhere will simply match the ``'^'`` character. For example,
178 ``[^5]`` will match any character except ``'5'``, and ``[^^]`` will match any
179 character except ``'^'``.
180
181``'|'``
182 ``A|B``, where A and B can be arbitrary REs, creates a regular expression that
183 will match either A or B. An arbitrary number of REs can be separated by the
184 ``'|'`` in this way. This can be used inside groups (see below) as well. As
185 the target string is scanned, REs separated by ``'|'`` are tried from left to
186 right. When one pattern completely matches, that branch is accepted. This means
187 that once ``A`` matches, ``B`` will not be tested further, even if it would
188 produce a longer overall match. In other words, the ``'|'`` operator is never
189 greedy. To match a literal ``'|'``, use ``\|``, or enclose it inside a
190 character class, as in ``[|]``.
191
192``(...)``
193 Matches whatever regular expression is inside the parentheses, and indicates the
194 start and end of a group; the contents of a group can be retrieved after a match
195 has been performed, and can be matched later in the string with the ``\number``
196 special sequence, described below. To match the literals ``'('`` or ``')'``,
197 use ``\(`` or ``\)``, or enclose them inside a character class: ``[(] [)]``.
198
199``(?...)``
200 This is an extension notation (a ``'?'`` following a ``'('`` is not meaningful
201 otherwise). The first character after the ``'?'`` determines what the meaning
202 and further syntax of the construct is. Extensions usually do not create a new
203 group; ``(?P<name>...)`` is the only exception to this rule. Following are the
204 currently supported extensions.
205
206``(?iLmsux)``
207 (One or more letters from the set ``'i'``, ``'L'``, ``'m'``, ``'s'``,
208 ``'u'``, ``'x'``.) The group matches the empty string; the letters
209 set the corresponding flags: :const:`re.I` (ignore case),
210 :const:`re.L` (locale dependent), :const:`re.M` (multi-line),
211 :const:`re.S` (dot matches all), :const:`re.U` (Unicode dependent),
212 and :const:`re.X` (verbose), for the entire regular expression. (The
213 flags are described in :ref:`contents-of-module-re`.) This
214 is useful if you wish to include the flags as part of the regular
215 expression, instead of passing a *flag* argument to the
216 :func:`compile` function.
217
218 Note that the ``(?x)`` flag changes how the expression is parsed. It should be
219 used first in the expression string, or after one or more whitespace characters.
220 If there are non-whitespace characters before the flag, the results are
221 undefined.
222
223``(?:...)``
224 A non-grouping version of regular parentheses. Matches whatever regular
225 expression is inside the parentheses, but the substring matched by the group
226 *cannot* be retrieved after performing a match or referenced later in the
227 pattern.
228
229``(?P<name>...)``
230 Similar to regular parentheses, but the substring matched by the group is
231 accessible via the symbolic group name *name*. Group names must be valid Python
232 identifiers, and each group name must be defined only once within a regular
233 expression. A symbolic group is also a numbered group, just as if the group
234 were not named. So the group named 'id' in the example below can also be
235 referenced as the numbered group 1.
236
237 For example, if the pattern is ``(?P<id>[a-zA-Z_]\w*)``, the group can be
238 referenced by its name in arguments to methods of match objects, such as
239 ``m.group('id')`` or ``m.end('id')``, and also by name in pattern text (for
240 example, ``(?P=id)``) and replacement text (such as ``\g<id>``).
241
242``(?P=name)``
243 Matches whatever text was matched by the earlier group named *name*.
244
245``(?#...)``
246 A comment; the contents of the parentheses are simply ignored.
247
248``(?=...)``
249 Matches if ``...`` matches next, but doesn't consume any of the string. This is
250 called a lookahead assertion. For example, ``Isaac (?=Asimov)`` will match
251 ``'Isaac '`` only if it's followed by ``'Asimov'``.
252
253``(?!...)``
254 Matches if ``...`` doesn't match next. This is a negative lookahead assertion.
255 For example, ``Isaac (?!Asimov)`` will match ``'Isaac '`` only if it's *not*
256 followed by ``'Asimov'``.
257
258``(?<=...)``
259 Matches if the current position in the string is preceded by a match for ``...``
260 that ends at the current position. This is called a :dfn:`positive lookbehind
261 assertion`. ``(?<=abc)def`` will find a match in ``abcdef``, since the
262 lookbehind will back up 3 characters and check if the contained pattern matches.
263 The contained pattern must only match strings of some fixed length, meaning that
264 ``abc`` or ``a|b`` are allowed, but ``a*`` and ``a{3,4}`` are not. Note that
265 patterns which start with positive lookbehind assertions will never match at the
266 beginning of the string being searched; you will most likely want to use the
267 :func:`search` function rather than the :func:`match` function::
268
269 >>> import re
270 >>> m = re.search('(?<=abc)def', 'abcdef')
271 >>> m.group(0)
272 'def'
273
274 This example looks for a word following a hyphen::
275
276 >>> m = re.search('(?<=-)\w+', 'spam-egg')
277 >>> m.group(0)
278 'egg'
279
280``(?<!...)``
281 Matches if the current position in the string is not preceded by a match for
282 ``...``. This is called a :dfn:`negative lookbehind assertion`. Similar to
283 positive lookbehind assertions, the contained pattern must only match strings of
284 some fixed length. Patterns which start with negative lookbehind assertions may
285 match at the beginning of the string being searched.
286
287``(?(id/name)yes-pattern|no-pattern)``
288 Will try to match with ``yes-pattern`` if the group with given *id* or *name*
289 exists, and with ``no-pattern`` if it doesn't. ``no-pattern`` is optional and
290 can be omitted. For example, ``(<)?(\w+@\w+(?:\.\w+)+)(?(1)>)`` is a poor email
291 matching pattern, which will match with ``'<user@host.com>'`` as well as
292 ``'user@host.com'``, but not with ``'<user@host.com'``.
293
294 .. versionadded:: 2.4
295
296The special sequences consist of ``'\'`` and a character from the list below.
297If the ordinary character is not on the list, then the resulting RE will match
298the second character. For example, ``\$`` matches the character ``'$'``.
299
Georg Brandl8ec7f652007-08-15 14:28:01 +0000300``\number``
301 Matches the contents of the group of the same number. Groups are numbered
302 starting from 1. For example, ``(.+) \1`` matches ``'the the'`` or ``'55 55'``,
303 but not ``'the end'`` (note the space after the group). This special sequence
304 can only be used to match one of the first 99 groups. If the first digit of
305 *number* is 0, or *number* is 3 octal digits long, it will not be interpreted as
306 a group match, but as the character with octal value *number*. Inside the
307 ``'['`` and ``']'`` of a character class, all numeric escapes are treated as
308 characters.
309
310``\A``
311 Matches only at the start of the string.
312
313``\b``
314 Matches the empty string, but only at the beginning or end of a word. A word is
315 defined as a sequence of alphanumeric or underscore characters, so the end of a
316 word is indicated by whitespace or a non-alphanumeric, non-underscore character.
317 Note that ``\b`` is defined as the boundary between ``\w`` and ``\ W``, so the
318 precise set of characters deemed to be alphanumeric depends on the values of the
319 ``UNICODE`` and ``LOCALE`` flags. Inside a character range, ``\b`` represents
320 the backspace character, for compatibility with Python's string literals.
321
322``\B``
323 Matches the empty string, but only when it is *not* at the beginning or end of a
324 word. This is just the opposite of ``\b``, so is also subject to the settings
325 of ``LOCALE`` and ``UNICODE``.
326
327``\d``
328 When the :const:`UNICODE` flag is not specified, matches any decimal digit; this
329 is equivalent to the set ``[0-9]``. With :const:`UNICODE`, it will match
330 whatever is classified as a digit in the Unicode character properties database.
331
332``\D``
333 When the :const:`UNICODE` flag is not specified, matches any non-digit
334 character; this is equivalent to the set ``[^0-9]``. With :const:`UNICODE`, it
335 will match anything other than character marked as digits in the Unicode
336 character properties database.
337
338``\s``
339 When the :const:`LOCALE` and :const:`UNICODE` flags are not specified, matches
340 any whitespace character; this is equivalent to the set ``[ \t\n\r\f\v]``. With
341 :const:`LOCALE`, it will match this set plus whatever characters are defined as
342 space for the current locale. If :const:`UNICODE` is set, this will match the
343 characters ``[ \t\n\r\f\v]`` plus whatever is classified as space in the Unicode
344 character properties database.
345
346``\S``
347 When the :const:`LOCALE` and :const:`UNICODE` flags are not specified, matches
348 any non-whitespace character; this is equivalent to the set ``[^ \t\n\r\f\v]``
349 With :const:`LOCALE`, it will match any character not in this set, and not
350 defined as space in the current locale. If :const:`UNICODE` is set, this will
351 match anything other than ``[ \t\n\r\f\v]`` and characters marked as space in
352 the Unicode character properties database.
353
354``\w``
355 When the :const:`LOCALE` and :const:`UNICODE` flags are not specified, matches
356 any alphanumeric character and the underscore; this is equivalent to the set
357 ``[a-zA-Z0-9_]``. With :const:`LOCALE`, it will match the set ``[0-9_]`` plus
358 whatever characters are defined as alphanumeric for the current locale. If
359 :const:`UNICODE` is set, this will match the characters ``[0-9_]`` plus whatever
360 is classified as alphanumeric in the Unicode character properties database.
361
362``\W``
363 When the :const:`LOCALE` and :const:`UNICODE` flags are not specified, matches
364 any non-alphanumeric character; this is equivalent to the set ``[^a-zA-Z0-9_]``.
365 With :const:`LOCALE`, it will match any character not in the set ``[0-9_]``, and
366 not defined as alphanumeric for the current locale. If :const:`UNICODE` is set,
367 this will match anything other than ``[0-9_]`` and characters marked as
368 alphanumeric in the Unicode character properties database.
369
370``\Z``
371 Matches only at the end of the string.
372
373Most of the standard escapes supported by Python string literals are also
374accepted by the regular expression parser::
375
376 \a \b \f \n
377 \r \t \v \x
378 \\
379
380Octal escapes are included in a limited form: If the first digit is a 0, or if
381there are three octal digits, it is considered an octal escape. Otherwise, it is
382a group reference. As for string literals, octal escapes are always at most
383three digits in length.
384
Georg Brandl8ec7f652007-08-15 14:28:01 +0000385
386.. _matching-searching:
387
388Matching vs Searching
389---------------------
390
391.. sectionauthor:: Fred L. Drake, Jr. <fdrake@acm.org>
392
393
394Python offers two different primitive operations based on regular expressions:
Georg Brandl604c1212007-08-23 21:36:05 +0000395**match** checks for a match only at the beginning of the string, while
396**search** checks for a match anywhere in the string (this is what Perl does
397by default).
Georg Brandl8ec7f652007-08-15 14:28:01 +0000398
Georg Brandl604c1212007-08-23 21:36:05 +0000399Note that match may differ from search even when using a regular expression
400beginning with ``'^'``: ``'^'`` matches only at the start of the string, or in
Georg Brandl8ec7f652007-08-15 14:28:01 +0000401:const:`MULTILINE` mode also immediately following a newline. The "match"
402operation succeeds only if the pattern matches at the start of the string
403regardless of mode, or at the starting position given by the optional *pos*
Georg Brandlb19be572007-12-29 10:57:00 +0000404argument regardless of whether a newline precedes it. ::
Georg Brandl8ec7f652007-08-15 14:28:01 +0000405
Georg Brandlb8df1562007-12-05 18:30:48 +0000406 >>> re.match("c", "abcdef") # No match
407 >>> re.search("c", "abcdef")
Georg Brandlb19be572007-12-29 10:57:00 +0000408 <_sre.SRE_Match object at 0x827e9c0> # Match
Georg Brandl8ec7f652007-08-15 14:28:01 +0000409
410
411.. _contents-of-module-re:
412
413Module Contents
414---------------
415
416The module defines several functions, constants, and an exception. Some of the
417functions are simplified versions of the full featured methods for compiled
418regular expressions. Most non-trivial applications always use the compiled
419form.
420
421
422.. function:: compile(pattern[, flags])
423
Georg Brandlba2e5192007-09-27 06:26:58 +0000424 Compile a regular expression pattern into a regular expression object, which
425 can be used for matching using its :func:`match` and :func:`search` methods,
Georg Brandl8ec7f652007-08-15 14:28:01 +0000426 described below.
427
428 The expression's behaviour can be modified by specifying a *flags* value.
429 Values can be any of the following variables, combined using bitwise OR (the
430 ``|`` operator).
431
432 The sequence ::
433
434 prog = re.compile(pat)
435 result = prog.match(str)
436
437 is equivalent to ::
438
439 result = re.match(pat, str)
440
Georg Brandlba2e5192007-09-27 06:26:58 +0000441 but the version using :func:`compile` is more efficient when the expression
442 will be used several times in a single program.
Georg Brandl8ec7f652007-08-15 14:28:01 +0000443
Georg Brandlb19be572007-12-29 10:57:00 +0000444 .. (The compiled version of the last pattern passed to :func:`re.match` or
445 :func:`re.search` is cached, so programs that use only a single regular
446 expression at a time needn't worry about compiling regular expressions.)
Georg Brandl8ec7f652007-08-15 14:28:01 +0000447
448
449.. data:: I
450 IGNORECASE
451
452 Perform case-insensitive matching; expressions like ``[A-Z]`` will match
453 lowercase letters, too. This is not affected by the current locale.
454
455
456.. data:: L
457 LOCALE
458
Georg Brandlba2e5192007-09-27 06:26:58 +0000459 Make ``\w``, ``\W``, ``\b``, ``\B``, ``\s`` and ``\S`` dependent on the
460 current locale.
Georg Brandl8ec7f652007-08-15 14:28:01 +0000461
462
463.. data:: M
464 MULTILINE
465
466 When specified, the pattern character ``'^'`` matches at the beginning of the
467 string and at the beginning of each line (immediately following each newline);
468 and the pattern character ``'$'`` matches at the end of the string and at the
469 end of each line (immediately preceding each newline). By default, ``'^'``
470 matches only at the beginning of the string, and ``'$'`` only at the end of the
471 string and immediately before the newline (if any) at the end of the string.
472
473
474.. data:: S
475 DOTALL
476
477 Make the ``'.'`` special character match any character at all, including a
478 newline; without this flag, ``'.'`` will match anything *except* a newline.
479
480
481.. data:: U
482 UNICODE
483
484 Make ``\w``, ``\W``, ``\b``, ``\B``, ``\d``, ``\D``, ``\s`` and ``\S`` dependent
485 on the Unicode character properties database.
486
487 .. versionadded:: 2.0
488
489
490.. data:: X
491 VERBOSE
492
493 This flag allows you to write regular expressions that look nicer. Whitespace
494 within the pattern is ignored, except when in a character class or preceded by
495 an unescaped backslash, and, when a line contains a ``'#'`` neither in a
496 character class or preceded by an unescaped backslash, all characters from the
497 leftmost such ``'#'`` through the end of the line are ignored.
498
Georg Brandlb8df1562007-12-05 18:30:48 +0000499 That means that the two following regular expression objects that match a
500 decimal number are functionally equal::
501
502 a = re.compile(r"""\d + # the integral part
503 \. # the decimal point
504 \d * # some fractional digits""", re.X)
505 b = re.compile(r"\d+\.\d*")
Georg Brandl8ec7f652007-08-15 14:28:01 +0000506
507
508.. function:: search(pattern, string[, flags])
509
510 Scan through *string* looking for a location where the regular expression
511 *pattern* produces a match, and return a corresponding :class:`MatchObject`
512 instance. Return ``None`` if no position in the string matches the pattern; note
513 that this is different from finding a zero-length match at some point in the
514 string.
515
516
517.. function:: match(pattern, string[, flags])
518
519 If zero or more characters at the beginning of *string* match the regular
520 expression *pattern*, return a corresponding :class:`MatchObject` instance.
521 Return ``None`` if the string does not match the pattern; note that this is
522 different from a zero-length match.
523
524 .. note::
525
Georg Brandlb8df1562007-12-05 18:30:48 +0000526 If you want to locate a match anywhere in *string*, use :meth:`search`
527 instead.
Georg Brandl8ec7f652007-08-15 14:28:01 +0000528
529
530.. function:: split(pattern, string[, maxsplit=0])
531
532 Split *string* by the occurrences of *pattern*. If capturing parentheses are
533 used in *pattern*, then the text of all groups in the pattern are also returned
534 as part of the resulting list. If *maxsplit* is nonzero, at most *maxsplit*
535 splits occur, and the remainder of the string is returned as the final element
536 of the list. (Incompatibility note: in the original Python 1.5 release,
537 *maxsplit* was ignored. This has been fixed in later releases.) ::
538
539 >>> re.split('\W+', 'Words, words, words.')
540 ['Words', 'words', 'words', '']
541 >>> re.split('(\W+)', 'Words, words, words.')
542 ['Words', ', ', 'words', ', ', 'words', '.', '']
543 >>> re.split('\W+', 'Words, words, words.', 1)
544 ['Words', 'words, words.']
545
Georg Brandl70992c32008-03-06 07:19:15 +0000546 If there are capturing groups in the separator and it matches at the start of
547 the string, the result will start with an empty string. The same holds for
548 the end of the string::
549
550 >>> re.split('(\W+)', '...words, words...')
551 ['', '...', 'words', ', ', 'words', '...', '']
552
553 That way, separator components are always found at the same relative
554 indices within the result list (e.g., if there's one capturing group
555 in the separator, the 0th, the 2nd and so forth).
556
Skip Montanaro222907d2007-09-01 17:40:03 +0000557 Note that *split* will never split a string on an empty pattern match.
Georg Brandl70992c32008-03-06 07:19:15 +0000558 For example::
Skip Montanaro222907d2007-09-01 17:40:03 +0000559
560 >>> re.split('x*', 'foo')
561 ['foo']
562 >>> re.split("(?m)^$", "foo\n\nbar\n")
563 ['foo\n\nbar\n']
Georg Brandl8ec7f652007-08-15 14:28:01 +0000564
Georg Brandl70992c32008-03-06 07:19:15 +0000565
Georg Brandl8ec7f652007-08-15 14:28:01 +0000566.. function:: findall(pattern, string[, flags])
567
Georg Brandlba2e5192007-09-27 06:26:58 +0000568 Return all non-overlapping matches of *pattern* in *string*, as a list of
569 strings. If one or more groups are present in the pattern, return a list of
570 groups; this will be a list of tuples if the pattern has more than one group.
571 Empty matches are included in the result unless they touch the beginning of
572 another match.
Georg Brandl8ec7f652007-08-15 14:28:01 +0000573
574 .. versionadded:: 1.5.2
575
576 .. versionchanged:: 2.4
577 Added the optional flags argument.
578
579
580.. function:: finditer(pattern, string[, flags])
581
Georg Brandle7a09902007-10-21 12:10:28 +0000582 Return an :term:`iterator` yielding :class:`MatchObject` instances over all
Georg Brandlba2e5192007-09-27 06:26:58 +0000583 non-overlapping matches for the RE *pattern* in *string*. Empty matches are
584 included in the result unless they touch the beginning of another match.
Georg Brandl8ec7f652007-08-15 14:28:01 +0000585
586 .. versionadded:: 2.2
587
588 .. versionchanged:: 2.4
589 Added the optional flags argument.
590
591
592.. function:: sub(pattern, repl, string[, count])
593
594 Return the string obtained by replacing the leftmost non-overlapping occurrences
595 of *pattern* in *string* by the replacement *repl*. If the pattern isn't found,
596 *string* is returned unchanged. *repl* can be a string or a function; if it is
597 a string, any backslash escapes in it are processed. That is, ``\n`` is
598 converted to a single newline character, ``\r`` is converted to a linefeed, and
599 so forth. Unknown escapes such as ``\j`` are left alone. Backreferences, such
600 as ``\6``, are replaced with the substring matched by group 6 in the pattern.
601 For example::
602
603 >>> re.sub(r'def\s+([a-zA-Z_][a-zA-Z_0-9]*)\s*\(\s*\):',
604 ... r'static PyObject*\npy_\1(void)\n{',
605 ... 'def myfunc():')
606 'static PyObject*\npy_myfunc(void)\n{'
607
608 If *repl* is a function, it is called for every non-overlapping occurrence of
609 *pattern*. The function takes a single match object argument, and returns the
610 replacement string. For example::
611
612 >>> def dashrepl(matchobj):
613 ... if matchobj.group(0) == '-': return ' '
614 ... else: return '-'
615 >>> re.sub('-{1,2}', dashrepl, 'pro----gram-files')
616 'pro--gram files'
617
618 The pattern may be a string or an RE object; if you need to specify regular
619 expression flags, you must use a RE object, or use embedded modifiers in a
620 pattern; for example, ``sub("(?i)b+", "x", "bbbb BBBB")`` returns ``'x x'``.
621
622 The optional argument *count* is the maximum number of pattern occurrences to be
623 replaced; *count* must be a non-negative integer. If omitted or zero, all
624 occurrences will be replaced. Empty matches for the pattern are replaced only
625 when not adjacent to a previous match, so ``sub('x*', '-', 'abc')`` returns
626 ``'-a-b-c-'``.
627
628 In addition to character escapes and backreferences as described above,
629 ``\g<name>`` will use the substring matched by the group named ``name``, as
630 defined by the ``(?P<name>...)`` syntax. ``\g<number>`` uses the corresponding
631 group number; ``\g<2>`` is therefore equivalent to ``\2``, but isn't ambiguous
632 in a replacement such as ``\g<2>0``. ``\20`` would be interpreted as a
633 reference to group 20, not a reference to group 2 followed by the literal
634 character ``'0'``. The backreference ``\g<0>`` substitutes in the entire
635 substring matched by the RE.
636
637
638.. function:: subn(pattern, repl, string[, count])
639
640 Perform the same operation as :func:`sub`, but return a tuple ``(new_string,
641 number_of_subs_made)``.
642
643
644.. function:: escape(string)
645
646 Return *string* with all non-alphanumerics backslashed; this is useful if you
647 want to match an arbitrary literal string that may have regular expression
648 metacharacters in it.
649
650
651.. exception:: error
652
653 Exception raised when a string passed to one of the functions here is not a
654 valid regular expression (for example, it might contain unmatched parentheses)
655 or when some other error occurs during compilation or matching. It is never an
656 error if a string contains no match for a pattern.
657
658
659.. _re-objects:
660
661Regular Expression Objects
662--------------------------
663
664Compiled regular expression objects support the following methods and
665attributes:
666
667
668.. method:: RegexObject.match(string[, pos[, endpos]])
669
670 If zero or more characters at the beginning of *string* match this regular
671 expression, return a corresponding :class:`MatchObject` instance. Return
672 ``None`` if the string does not match the pattern; note that this is different
673 from a zero-length match.
674
675 .. note::
676
Georg Brandlb8df1562007-12-05 18:30:48 +0000677 If you want to locate a match anywhere in *string*, use :meth:`search`
678 instead.
Georg Brandl8ec7f652007-08-15 14:28:01 +0000679
680 The optional second parameter *pos* gives an index in the string where the
681 search is to start; it defaults to ``0``. This is not completely equivalent to
682 slicing the string; the ``'^'`` pattern character matches at the real beginning
683 of the string and at positions just after a newline, but not necessarily at the
684 index where the search is to start.
685
686 The optional parameter *endpos* limits how far the string will be searched; it
687 will be as if the string is *endpos* characters long, so only the characters
688 from *pos* to ``endpos - 1`` will be searched for a match. If *endpos* is less
689 than *pos*, no match will be found, otherwise, if *rx* is a compiled regular
690 expression object, ``rx.match(string, 0, 50)`` is equivalent to
Georg Brandlb8df1562007-12-05 18:30:48 +0000691 ``rx.match(string[:50], 0)``. ::
692
693 >>> pattern = re.compile("o")
694 >>> pattern.match("dog") # No match as "o" is not at the start of "dog."
695 >>> pattern.match("dog", 1) # Match as "o" is the 2nd character of "dog".
696 <_sre.SRE_Match object at 0x827eb10>
Georg Brandl8ec7f652007-08-15 14:28:01 +0000697
698
699.. method:: RegexObject.search(string[, pos[, endpos]])
700
701 Scan through *string* looking for a location where this regular expression
702 produces a match, and return a corresponding :class:`MatchObject` instance.
703 Return ``None`` if no position in the string matches the pattern; note that this
704 is different from finding a zero-length match at some point in the string.
705
706 The optional *pos* and *endpos* parameters have the same meaning as for the
707 :meth:`match` method.
708
709
710.. method:: RegexObject.split(string[, maxsplit=0])
711
712 Identical to the :func:`split` function, using the compiled pattern.
713
714
715.. method:: RegexObject.findall(string[, pos[, endpos]])
716
717 Identical to the :func:`findall` function, using the compiled pattern.
718
719
720.. method:: RegexObject.finditer(string[, pos[, endpos]])
721
722 Identical to the :func:`finditer` function, using the compiled pattern.
723
724
725.. method:: RegexObject.sub(repl, string[, count=0])
726
727 Identical to the :func:`sub` function, using the compiled pattern.
728
729
730.. method:: RegexObject.subn(repl, string[, count=0])
731
732 Identical to the :func:`subn` function, using the compiled pattern.
733
734
735.. attribute:: RegexObject.flags
736
737 The flags argument used when the RE object was compiled, or ``0`` if no flags
738 were provided.
739
740
741.. attribute:: RegexObject.groupindex
742
743 A dictionary mapping any symbolic group names defined by ``(?P<id>)`` to group
744 numbers. The dictionary is empty if no symbolic groups were used in the
745 pattern.
746
747
748.. attribute:: RegexObject.pattern
749
750 The pattern string from which the RE object was compiled.
751
752
753.. _match-objects:
754
755Match Objects
756-------------
757
Georg Brandlba2e5192007-09-27 06:26:58 +0000758Match objects always have a boolean value of :const:`True`, so that you can test
759whether e.g. :func:`match` resulted in a match with a simple if statement. They
760support the following methods and attributes:
Georg Brandl8ec7f652007-08-15 14:28:01 +0000761
762
763.. method:: MatchObject.expand(template)
764
765 Return the string obtained by doing backslash substitution on the template
766 string *template*, as done by the :meth:`sub` method. Escapes such as ``\n`` are
767 converted to the appropriate characters, and numeric backreferences (``\1``,
768 ``\2``) and named backreferences (``\g<1>``, ``\g<name>``) are replaced by the
769 contents of the corresponding group.
770
771
772.. method:: MatchObject.group([group1, ...])
773
774 Returns one or more subgroups of the match. If there is a single argument, the
775 result is a single string; if there are multiple arguments, the result is a
776 tuple with one item per argument. Without arguments, *group1* defaults to zero
777 (the whole match is returned). If a *groupN* argument is zero, the corresponding
778 return value is the entire matching string; if it is in the inclusive range
779 [1..99], it is the string matching the corresponding parenthesized group. If a
780 group number is negative or larger than the number of groups defined in the
781 pattern, an :exc:`IndexError` exception is raised. If a group is contained in a
782 part of the pattern that did not match, the corresponding result is ``None``.
783 If a group is contained in a part of the pattern that matched multiple times,
Georg Brandlb8df1562007-12-05 18:30:48 +0000784 the last match is returned. ::
785
786 >>> m = re.match(r"(\w+) (\w+)", "Isaac Newton, physicist")
787 >>> m.group(0)
788 'Isaac Newton' # The entire match
789 >>> m.group(1)
790 'Isaac' # The first parenthesized subgroup.
791 >>> m.group(2)
792 'Newton' # The second parenthesized subgroup.
793 >>> m.group(1, 2)
794 ('Isaac', 'Newton') # Multiple arguments give us a tuple.
Georg Brandl8ec7f652007-08-15 14:28:01 +0000795
796 If the regular expression uses the ``(?P<name>...)`` syntax, the *groupN*
797 arguments may also be strings identifying groups by their group name. If a
798 string argument is not used as a group name in the pattern, an :exc:`IndexError`
799 exception is raised.
800
801 A moderately complicated example::
802
Georg Brandlb8df1562007-12-05 18:30:48 +0000803 >>> m = re.match(r"(?P<first_name>\w+) (?P<last_name>\w+)", "Malcom Reynolds")
804 >>> m.group('first_name')
805 'Malcom'
806 >>> m.group('last_name')
807 'Reynolds'
Georg Brandl8ec7f652007-08-15 14:28:01 +0000808
Georg Brandlb8df1562007-12-05 18:30:48 +0000809 Named groups can also be referred to by their index::
810
811 >>> m.group(1)
812 'Malcom'
813 >>> m.group(2)
814 'Reynolds'
815
816 If a group matches multiple times, only the last match is accessible::
817 >>> m = re.match(r"(..)+", "a1b2c3") # Matches 3 times.
818 >>> m.group(1) # Returns only the last match.
819 'c3'
Georg Brandl8ec7f652007-08-15 14:28:01 +0000820
821
822.. method:: MatchObject.groups([default])
823
824 Return a tuple containing all the subgroups of the match, from 1 up to however
825 many groups are in the pattern. The *default* argument is used for groups that
826 did not participate in the match; it defaults to ``None``. (Incompatibility
827 note: in the original Python 1.5 release, if the tuple was one element long, a
828 string would be returned instead. In later versions (from 1.5.1 on), a
829 singleton tuple is returned in such cases.)
830
Georg Brandlb8df1562007-12-05 18:30:48 +0000831 For example::
832
833 >>> m = re.match(r"(\d+)\.(\d+)", "24.1632")
834 >>> m.groups()
835 ('24', '1632')
836
837 If we make the decimal place and everything after it optional, not all groups
838 might participate in the match. These groups will default to ``None`` unless
839 the *default* argument is given::
840
841 >>> m = re.match(r"(\d+)\.?(\d+)?", "24")
842 >>> m.groups()
843 ('24', None) # Second group defaults to None.
844 >>> m.groups('0')
845 ('24', '0') # Now, the second group defaults to '0'.
846
Georg Brandl8ec7f652007-08-15 14:28:01 +0000847
848.. method:: MatchObject.groupdict([default])
849
850 Return a dictionary containing all the *named* subgroups of the match, keyed by
851 the subgroup name. The *default* argument is used for groups that did not
Georg Brandlb8df1562007-12-05 18:30:48 +0000852 participate in the match; it defaults to ``None``. For example::
853
854 >>> m = re.match(r"(?P<first_name>\w+) (?P<last_name>\w+)", "Malcom Reynolds")
855 >>> m.groupdict()
856 {'first_name': 'Malcom', 'last_name': 'Reynolds'}
Georg Brandl8ec7f652007-08-15 14:28:01 +0000857
858
859.. method:: MatchObject.start([group])
860 MatchObject.end([group])
861
862 Return the indices of the start and end of the substring matched by *group*;
863 *group* defaults to zero (meaning the whole matched substring). Return ``-1`` if
864 *group* exists but did not contribute to the match. For a match object *m*, and
865 a group *g* that did contribute to the match, the substring matched by group *g*
866 (equivalent to ``m.group(g)``) is ::
867
868 m.string[m.start(g):m.end(g)]
869
870 Note that ``m.start(group)`` will equal ``m.end(group)`` if *group* matched a
871 null string. For example, after ``m = re.search('b(c?)', 'cba')``,
872 ``m.start(0)`` is 1, ``m.end(0)`` is 2, ``m.start(1)`` and ``m.end(1)`` are both
873 2, and ``m.start(2)`` raises an :exc:`IndexError` exception.
874
Georg Brandlb8df1562007-12-05 18:30:48 +0000875 An example that will remove *remove_this* from email addresses::
876
877 >>> email = "tony@tiremove_thisger.net"
878 >>> m = re.search("remove_this", email)
879 >>> email[:m.start()] + email[m.end():]
880 'tony@tiger.net'
881
Georg Brandl8ec7f652007-08-15 14:28:01 +0000882
883.. method:: MatchObject.span([group])
884
885 For :class:`MatchObject` *m*, return the 2-tuple ``(m.start(group),
886 m.end(group))``. Note that if *group* did not contribute to the match, this is
Georg Brandlb8df1562007-12-05 18:30:48 +0000887 ``(-1, -1)``. *group* defaults to zero, the entire match.
Georg Brandl8ec7f652007-08-15 14:28:01 +0000888
889
890.. attribute:: MatchObject.pos
891
892 The value of *pos* which was passed to the :func:`search` or :func:`match`
893 method of the :class:`RegexObject`. This is the index into the string at which
894 the RE engine started looking for a match.
895
896
897.. attribute:: MatchObject.endpos
898
899 The value of *endpos* which was passed to the :func:`search` or :func:`match`
900 method of the :class:`RegexObject`. This is the index into the string beyond
901 which the RE engine will not go.
902
903
904.. attribute:: MatchObject.lastindex
905
906 The integer index of the last matched capturing group, or ``None`` if no group
907 was matched at all. For example, the expressions ``(a)b``, ``((a)(b))``, and
908 ``((ab))`` will have ``lastindex == 1`` if applied to the string ``'ab'``, while
909 the expression ``(a)(b)`` will have ``lastindex == 2``, if applied to the same
910 string.
911
912
913.. attribute:: MatchObject.lastgroup
914
915 The name of the last matched capturing group, or ``None`` if the group didn't
916 have a name, or if no group was matched at all.
917
918
919.. attribute:: MatchObject.re
920
921 The regular expression object whose :meth:`match` or :meth:`search` method
922 produced this :class:`MatchObject` instance.
923
924
925.. attribute:: MatchObject.string
926
927 The string passed to :func:`match` or :func:`search`.
928
929
930Examples
931--------
932
Georg Brandlb8df1562007-12-05 18:30:48 +0000933
934Checking For a Pair
935^^^^^^^^^^^^^^^^^^^
936
937In this example, we'll use the following helper function to display match
938objects a little more gracefully::
939
940 def displaymatch(match):
941 if match is None:
942 return None
943 return '<Match: %r, groups=%r>' % (match.group(), match.groups())
944
945Suppose you are writing a poker program where a player's hand is represented as
946a 5-character string with each character representing a card, "a" for ace, "k"
947for king, "q" for queen, j for jack, "0" for 10, and "1" through "9"
948representing the card with that value.
949
950To see if a given string is a valid hand, one could do the following::
951
952 >>> valid = re.compile(r"[0-9akqj]{5}$"
953 >>> displaymatch(valid.match("ak05q")) # Valid.
954 <Match: 'ak05q', groups=()>
955 >>> displaymatch(valid.match("ak05e")) # Invalid.
956 >>> displaymatch(valid.match("ak0")) # Invalid.
957 >>> displaymatch(valid.match("727ak")) # Valid.
958 <Match: '727ak', groups=()>
959
960That last hand, ``"727ak"``, contained a pair, or two of the same valued cards.
961To match this with a regular expression, one could use backreferences as such::
962
963 >>> pair = re.compile(r".*(.).*\1")
964 >>> displaymatch(pair.match("717ak")) # Pair of 7s.
965 <Match: '717', groups=('7',)>
966 >>> displaymatch(pair.match("718ak")) # No pairs.
967 >>> displaymatch(pair.match("354aa")) # Pair of aces.
968 <Match: '345aa', groups=('a',)>
969
970To find out what card the pair consists of, one could use the :func:`group`
971method of :class:`MatchObject` in the following manner::
972
973 >>> pair.match("717ak").group(1)
974 '7'
975
976 # Error because re.match() returns None, which doesn't have a group() method:
977 >>> pair.match("718ak").group(1)
978 Traceback (most recent call last):
979 File "<pyshell#23>", line 1, in <module>
980 re.match(r".*(.).*\1", "718ak").group(1)
981 AttributeError: 'NoneType' object has no attribute 'group'
982
983 >>> pair.match("354aa").group(1)
984 'a'
985
986
987Simulating scanf()
988^^^^^^^^^^^^^^^^^^
Georg Brandl8ec7f652007-08-15 14:28:01 +0000989
990.. index:: single: scanf()
991
992Python does not currently have an equivalent to :cfunc:`scanf`. Regular
993expressions are generally more powerful, though also more verbose, than
994:cfunc:`scanf` format strings. The table below offers some more-or-less
995equivalent mappings between :cfunc:`scanf` format tokens and regular
996expressions.
997
998+--------------------------------+---------------------------------------------+
999| :cfunc:`scanf` Token | Regular Expression |
1000+================================+=============================================+
1001| ``%c`` | ``.`` |
1002+--------------------------------+---------------------------------------------+
1003| ``%5c`` | ``.{5}`` |
1004+--------------------------------+---------------------------------------------+
1005| ``%d`` | ``[-+]?\d+`` |
1006+--------------------------------+---------------------------------------------+
1007| ``%e``, ``%E``, ``%f``, ``%g`` | ``[-+]?(\d+(\.\d*)?|\.\d+)([eE][-+]?\d+)?`` |
1008+--------------------------------+---------------------------------------------+
1009| ``%i`` | ``[-+]?(0[xX][\dA-Fa-f]+|0[0-7]*|\d+)`` |
1010+--------------------------------+---------------------------------------------+
1011| ``%o`` | ``0[0-7]*`` |
1012+--------------------------------+---------------------------------------------+
1013| ``%s`` | ``\S+`` |
1014+--------------------------------+---------------------------------------------+
1015| ``%u`` | ``\d+`` |
1016+--------------------------------+---------------------------------------------+
1017| ``%x``, ``%X`` | ``0[xX][\dA-Fa-f]+`` |
1018+--------------------------------+---------------------------------------------+
1019
1020To extract the filename and numbers from a string like ::
1021
1022 /usr/sbin/sendmail - 0 errors, 4 warnings
1023
1024you would use a :cfunc:`scanf` format like ::
1025
1026 %s - %d errors, %d warnings
1027
1028The equivalent regular expression would be ::
1029
1030 (\S+) - (\d+) errors, (\d+) warnings
1031
Georg Brandlb8df1562007-12-05 18:30:48 +00001032
1033Avoiding recursion
1034^^^^^^^^^^^^^^^^^^
Georg Brandl8ec7f652007-08-15 14:28:01 +00001035
1036If you create regular expressions that require the engine to perform a lot of
1037recursion, you may encounter a :exc:`RuntimeError` exception with the message
1038``maximum recursion limit`` exceeded. For example, ::
1039
1040 >>> import re
1041 >>> s = 'Begin ' + 1000*'a very long string ' + 'end'
1042 >>> re.match('Begin (\w| )*? end', s).end()
1043 Traceback (most recent call last):
1044 File "<stdin>", line 1, in ?
1045 File "/usr/local/lib/python2.5/re.py", line 132, in match
1046 return _compile(pattern, flags).match(string)
1047 RuntimeError: maximum recursion limit exceeded
1048
1049You can often restructure your regular expression to avoid recursion.
1050
1051Starting with Python 2.3, simple uses of the ``*?`` pattern are special-cased to
1052avoid recursion. Thus, the above regular expression can avoid recursion by
1053being recast as ``Begin [a-zA-Z0-9_ ]*?end``. As a further benefit, such
1054regular expressions will run faster than their recursive equivalents.
1055
Georg Brandlb8df1562007-12-05 18:30:48 +00001056
1057search() vs. match()
1058^^^^^^^^^^^^^^^^^^^^
1059
1060In a nutshell, :func:`match` only attempts to match a pattern at the beginning
1061of a string where :func:`search` will match a pattern anywhere in a string.
1062For example::
1063
1064 >>> re.match("o", "dog") # No match as "o" is not the first letter of "dog".
1065 >>> re.search("o", "dog") # Match as search() looks everywhere in the string.
1066 <_sre.SRE_Match object at 0x827e9f8>
1067
1068.. note::
1069
1070 The following applies only to regular expression objects like those created
1071 with ``re.compile("pattern")``, not the primitives
1072 ``re.match(pattern, string)`` or ``re.search(pattern, string)``.
1073
1074:func:`match` has an optional second parameter that gives an index in the string
1075where the search is to start::
1076
1077 >>> pattern = re.compile("o")
1078 >>> pattern.match("dog") # No match as "o" is not at the start of "dog."
1079 # Equivalent to the above expression as 0 is the default starting index:
1080 >>> pattern.match("dog", 0)
1081 # Match as "o" is the 2nd character of "dog" (index 0 is the first):
1082 >>> pattern.match("dog", 1)
1083 <_sre.SRE_Match object at 0x827eb10>
1084 >>> pattern.match("dog", 2) # No match as "o" is not the 3rd character of "dog."
1085
1086
1087Making a Phonebook
1088^^^^^^^^^^^^^^^^^^
1089
1090:func:`split` splits a string into a list delimited by the passed pattern. The
1091method is invaluable for converting textual data into data structures that can be
1092easily read and modified by Python as demonstrated in the following example that
1093creates a phonebook.
1094
Georg Brandld6b20dc2007-12-06 09:45:39 +00001095First, here is the input. Normally it may come from a file, here we are using
1096triple-quoted string syntax::
Georg Brandlb8df1562007-12-05 18:30:48 +00001097
Georg Brandld6b20dc2007-12-06 09:45:39 +00001098 >>> input = """Ross McFluff: 834.345.1254 155 Elm Street
Georg Brandlb8df1562007-12-05 18:30:48 +00001099
Georg Brandld6b20dc2007-12-06 09:45:39 +00001100 Ronald Heathmore: 892.345.3428 436 Finley Avenue
1101 Frank Burger: 925.541.7625 662 South Dogwood Way
Georg Brandlb8df1562007-12-05 18:30:48 +00001102
Georg Brandld6b20dc2007-12-06 09:45:39 +00001103
1104 Heather Albrecht: 548.326.4584 919 Park Place"""
1105
1106The entries are separated by one or more newlines. Now we convert the string
1107into a list with each nonempty line having its own entry::
1108
1109 >>> entries = re.split("\n+", input)
Georg Brandlb8df1562007-12-05 18:30:48 +00001110 >>> entries
1111 ['Ross McFluff 834.345.1254 155 Elm Street',
1112 'Ronald Heathmore 892.345.3428 436 Finley Avenue',
1113 'Frank Burger 925.541.7625 662 South Dogwood Way',
1114 'Heather Albrecht 548.326.4584 919 Park Place']
1115
1116Finally, split each entry into a list with first name, last name, telephone
Georg Brandl907a7202008-02-22 12:31:45 +00001117number, and address. We use the ``maxsplit`` parameter of :func:`split`
Georg Brandlb8df1562007-12-05 18:30:48 +00001118because the address has spaces, our splitting pattern, in it::
1119
Georg Brandld6b20dc2007-12-06 09:45:39 +00001120 >>> [re.split(":? ", entry, 3) for entry in entries]
Georg Brandlb8df1562007-12-05 18:30:48 +00001121 [['Ross', 'McFluff', '834.345.1254', '155 Elm Street'],
1122 ['Ronald', 'Heathmore', '892.345.3428', '436 Finley Avenue'],
1123 ['Frank', 'Burger', '925.541.7625', '662 South Dogwood Way'],
1124 ['Heather', 'Albrecht', '548.326.4584', '919 Park Place']]
1125
Georg Brandld6b20dc2007-12-06 09:45:39 +00001126The ``:?`` pattern matches the colon after the last name, so that it does not
Georg Brandl907a7202008-02-22 12:31:45 +00001127occur in the result list. With a ``maxsplit`` of ``4``, we could separate the
Georg Brandld6b20dc2007-12-06 09:45:39 +00001128house number from the street name::
Georg Brandlb8df1562007-12-05 18:30:48 +00001129
Georg Brandld6b20dc2007-12-06 09:45:39 +00001130 >>> [re.split(":? ", entry, 4) for entry in entries]
Georg Brandlb8df1562007-12-05 18:30:48 +00001131 [['Ross', 'McFluff', '834.345.1254', '155', 'Elm Street'],
1132 ['Ronald', 'Heathmore', '892.345.3428', '436', 'Finley Avenue'],
1133 ['Frank', 'Burger', '925.541.7625', '662', 'South Dogwood Way'],
1134 ['Heather', 'Albrecht', '548.326.4584', '919', 'Park Place']]
1135
1136
1137Text Munging
1138^^^^^^^^^^^^
1139
1140:func:`sub` replaces every occurrence of a pattern with a string or the
1141result of a function. This example demonstrates using :func:`sub` with
1142a function to "munge" text, or randomize the order of all the characters
1143in each word of a sentence except for the first and last characters::
1144
1145 >>> def repl(m):
1146 ... inner_word = list(m.group(2))
1147 ... random.shuffle(inner_word)
1148 ... return m.group(1) + "".join(inner_word) + m.group(3)
1149 >>> text = "Professor Abdolmalek, please report your absences promptly."
1150 >>> re.sub("(\w)(\w+)(\w)", repl, text)
1151 'Poefsrosr Aealmlobdk, pslaee reorpt your abnseces plmrptoy.'
1152 >>> re.sub("(\w)(\w+)(\w)", repl, text)
1153 'Pofsroser Aodlambelk, plasee reoprt yuor asnebces potlmrpy.'
1154
1155
1156Finding all Adverbs
1157^^^^^^^^^^^^^^^^^^^
1158
Georg Brandl907a7202008-02-22 12:31:45 +00001159:func:`findall` matches *all* occurrences of a pattern, not just the first
Georg Brandlb8df1562007-12-05 18:30:48 +00001160one as :func:`search` does. For example, if one was a writer and wanted to
1161find all of the adverbs in some text, he or she might use :func:`findall` in
1162the following manner::
1163
1164 >>> text = "He was carefully disguised but captured quickly by police."
1165 >>> re.findall(r"\w+ly", text)
1166 ['carefully', 'quickly']
1167
1168
1169Finding all Adverbs and their Positions
1170^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1171
1172If one wants more information about all matches of a pattern than the matched
1173text, :func:`finditer` is useful as it provides instances of
1174:class:`MatchObject` instead of strings. Continuing with the previous example,
1175if one was a writer who wanted to find all of the adverbs *and their positions*
1176in some text, he or she would use :func:`finditer` in the following manner::
1177
1178 >>> text = "He was carefully disguised but captured quickly by police."
1179 >>> for m in re.finditer(r"\w+ly", text):
1180 print '%02d-%02d: %s' % (m.start(), m.end(), m.group(0))
1181 07-16: carefully
1182 40-47: quickly
1183
1184
1185Raw String Notation
1186^^^^^^^^^^^^^^^^^^^
1187
1188Raw string notation (``r"text"``) keeps regular expressions sane. Without it,
1189every backslash (``'\'``) in a regular expression would have to be prefixed with
1190another one to escape it. For example, the two following lines of code are
1191functionally identical::
1192
1193 >>> re.match(r"\W(.)\1\W", " ff ")
1194 <_sre.SRE_Match object at 0x8262760>
1195 >>> re.match("\\W(.)\\1\\W", " ff ")
1196 <_sre.SRE_Match object at 0x82627a0>
1197
1198When one wants to match a literal backslash, it must be escaped in the regular
1199expression. With raw string notation, this means ``r"\\"``. Without raw string
1200notation, one must use ``"\\\\"``, making the following lines of code
1201functionally identical::
1202
1203 >>> re.match(r"\\", r"\\")
1204 <_sre.SRE_Match object at 0x827eb48>
1205 >>> re.match("\\\\", r"\\")
1206 <_sre.SRE_Match object at 0x827ec60>