<!DOCTYPE html PUBLIC
"-//W3C//DTD HTML 4.0 Transitional//EN">
<link rel=
"STYLESHEET" href=
"lib.css" type='text/css'
/>
<link rel=
"SHORTCUT ICON" href=
"../icons/pyfav.png" type=
"image/png" />
<link rel='start' href='../index.html' title='Python Documentation Index'
/>
<link rel=
"first" href=
"lib.html" title='Python Library Reference'
/>
<link rel='contents' href='contents.html'
title=
"Contents" />
<link rel='index' href='genindex.html' title='Index'
/>
<link rel='last' href='about.html' title='About this document...'
/>
<link rel='help' href='about.html' title='About this document...'
/>
<link rel=
"next" href=
"matching-searching.html" />
<link rel=
"prev" href=
"module-re.html" />
<link rel=
"parent" href=
"module-re.html" />
<link rel=
"next" href=
"matching-searching.html" />
<meta name='aesop' content='information'
/>
<title>4.2.1 Regular Expression Syntax
</title>
<div id='top-navigation-panel' xml:id='top-navigation-panel'
>
<table align=
"center" width=
"100%" cellpadding=
"0" cellspacing=
"2">
<td class='online-navigation'
><a rel=
"prev" title=
"4.2 re "
href=
"module-re.html"><img src='../icons/previous.png'
border='
0' height='
32' alt='Previous Page' width='
32'
/></A></td><td class='online-navigation'
><a rel=
"parent" title=
"4.2 re "
href=
"module-re.html"><img src='../icons/up.png'
border='
0' height='
32' alt='Up One Level' width='
32'
/></A></td><td class='online-navigation'
><a rel=
"next" title=
"4.2.2 Matching vs Searching"
href=
"matching-searching.html"><img src='../icons/next.png'
border='
0' height='
32' alt='Next Page' width='
32'
/></A></td><td align=
"center" width=
"100%">Python Library Reference
</td>
<td class='online-navigation'
><a rel=
"contents" title=
"Table of Contents"
href=
"contents.html"><img src='../icons/contents.png'
border='
0' height='
32' alt='Contents' width='
32'
/></A></td><td class='online-navigation'
><a href=
"modindex.html" title=
"Module Index"><img src='../icons/modules.png'
border='
0' height='
32' alt='Module Index' width='
32'
/></a></td><td class='online-navigation'
><a rel=
"index" title=
"Index"
href=
"genindex.html"><img src='../icons/index.png'
border='
0' height='
32' alt='Index' width='
32'
/></A></td><div class='online-navigation'
>
<b class=
"navlabel">Previous:
</b>
<a class=
"sectref" rel=
"prev" href=
"module-re.html">4.2 re
</A>
<b class=
"navlabel">Up:
</b>
<a class=
"sectref" rel=
"parent" href=
"module-re.html">4.2 re
</A>
<b class=
"navlabel">Next:
</b>
<a class=
"sectref" rel=
"next" href=
"matching-searching.html">4.2.2 Matching vs Searching
</A>
<!--End of Navigation Panel-->
<H2><A NAME=
"SECTION006210000000000000000"></A><A NAME=
"re-syntax"></A>
4.2.1 Regular Expression Syntax
A regular expression (or RE) specifies a set of strings that matches
it; the functions in this module let you check if a particular string
matches a given regular expression (or if a given regular expression
matches a particular string, which comes down to the same thing).
Regular expressions can be concatenated to form new regular
expressions; if
<em>A
</em> and
<em>B
</em> are both regular expressions,
then
<em>AB
</em> is also a regular expression. In general, if a string
<em>p
</em> matches
<em>A
</em> and another string
<em>q
</em> matches
<em>B
</em>,
the string
<em>pq
</em> will match AB. This holds unless
<em>A
</em> or
<em>B
</em> contain low precedence operations; boundary conditions between
<em>A
</em> and
<em>B
</em>; or have numbered group references. Thus, complex
expressions can easily be constructed from simpler primitive
expressions like the ones described here. For details of the theory
and implementation of regular expressions, consult the Friedl book
referenced above, or almost any textbook about compiler construction.
A brief explanation of the format of regular expressions follows. For
further information and a gentler presentation, consult the Regular
Expression HOWTO, accessible from
<a class=
"url" href=
"http://www.python.org/doc/howto/">http://www.python.org/doc/howto/
</a>.
Regular expressions can contain both special and ordinary characters.
Most ordinary characters, like
"<tt class="character
">A</tt>",
"<tt class="character
">a</tt>", or
"<tt class="character
">0</tt>", are the simplest regular expressions; they simply match
themselves. You can concatenate ordinary characters, so
<tt class=
"regexp">last
</tt>matches the string
<code>'last'
</code>. (In the rest of this section, we'll
write RE's in
<tt class=
"regexp">this special style
</tt>, usually without quotes, and
strings to be matched
<code>'in single quotes'
</code>.)
Some characters, like
"<tt class="character
">|</tt>" or
"<tt class="character
">(</tt>", are special.
Special characters either stand for classes of ordinary characters, or
affect how the regular expressions around them are interpreted.
The special characters are:
<DT><STRONG>"<tt class="character
">.</tt>"</STRONG></DT>
<DD>(Dot.) In the default mode, this matches any
character except a newline. If the
<tt class=
"constant">DOTALL
</tt> flag has been
specified, this matches any character including a newline.
<DT><STRONG>"<tt class="character
">^</tt>"</STRONG></DT>
<DD>(Caret.) Matches the start of the
string, and in
<tt class=
"constant">MULTILINE
</tt> mode also matches immediately
<DT><STRONG>"<tt class="character
">$</tt>"</STRONG></DT>
<DD>Matches the end of the string or just before the
newline at the end of the string, and in
<tt class=
"constant">MULTILINE
</tt> mode
also matches before a newline.
<tt class=
"regexp">foo
</tt> matches both 'foo' and
'foobar', while the regular expression
<tt class=
"regexp">foo$
</tt> matches only
'foo'. More interestingly, searching for
<tt class=
"regexp">foo.$
</tt> in
'foo1
\nfoo2
\n' matches 'foo2' normally,
but 'foo1' in
<tt class=
"constant">MULTILINE
</tt> mode.
<DT><STRONG>"<tt class="character
">*</tt>"</STRONG></DT>
<DD>Causes the resulting RE to
match
0 or more repetitions of the preceding RE, as many repetitions
as are possible.
<tt class=
"regexp">ab*
</tt> will
match 'a', 'ab', or 'a' followed by any number of 'b's.
<DT><STRONG>"<tt class="character
">+</tt>"</STRONG></DT>
resulting RE to match
1 or more repetitions of the preceding RE.
<tt class=
"regexp">ab+
</tt> will match 'a' followed by any non-zero number of 'b's; it
<DT><STRONG>"<tt class="character
">?</tt>"</STRONG></DT>
<DD>Causes the resulting RE to
match
0 or
1 repetitions of the preceding RE.
<tt class=
"regexp">ab?
</tt> will
match either 'a' or 'ab'.
<DT><STRONG><code>*?
</code>,
<code>+?
</code>,
<code>??
</code></STRONG></DT>
<DD>The
"<tt class="character
">*</tt>",
"<tt class="character
">+</tt>", and
"<tt class="character
">?</tt>" qualifiers are all
<i class=
"dfn">greedy
</i>; they
match as much text as possible. Sometimes this behaviour isn't
desired; if the RE
<tt class=
"regexp"><.*
></tt> is matched against
<code>'
<H1
>title
</H1
>'
</code>, it will match the entire string, and not just
<code>'
<H1
>'
</code>. Adding
"<tt class="character
">?</tt>" after the qualifier makes it
perform the match in
<i class=
"dfn">non-greedy
</i> or
<i class=
"dfn">minimal
</i> fashion; as
<em>few
</em> characters as possible will be matched. Using
<tt class=
"regexp">.*?
</tt>
in the previous expression will match only
<code>'
<H1
>'
</code>.
<DT><STRONG><code>{
<var>m
</var>}
</code></STRONG></DT>
<DD>Specifies that exactly
<var>m
</var> copies of the previous RE should be
matched; fewer matches cause the entire RE not to match. For example,
<tt class=
"regexp">a{
6}
</tt> will match exactly six
"<tt class="character
">a</tt>" characters, but
<DT><STRONG><code>{
<var>m
</var>,
<var>n
</var>}
</code></STRONG></DT>
<DD>Causes the resulting RE to match from
<var>m
</var> to
<var>n
</var> repetitions of the preceding RE, attempting to
match as many repetitions as possible. For example,
<tt class=
"regexp">a{
3,
5}
</tt>will match from
3 to
5 "<tt class="character
">a</tt>" characters. Omitting
<var>m
</var>specifies a lower bound of zero,
and omitting
<var>n
</var> specifies an infinite upper bound. As an
example,
<tt class=
"regexp">a{
4,}b
</tt> will match
<code>aaaab
</code> or a thousand
"<tt class="character
">a</tt>" characters followed by a
<code>b
</code>, but not
<code>aaab
</code>.
The comma may not be omitted or the modifier would be confused with
the previously described form.
<DT><STRONG><code>{
<var>m
</var>,
<var>n
</var>}?
</code></STRONG></DT>
<DD>Causes the resulting RE to
match from
<var>m
</var> to
<var>n
</var> repetitions of the preceding RE,
attempting to match as
<em>few
</em> repetitions as possible. This is
the non-greedy version of the previous qualifier. For example, on the
6-character string
<code>'aaaaaa'
</code>,
<tt class=
"regexp">a{
3,
5}
</tt> will match
5
"<tt class="character
">a</tt>" characters, while
<tt class=
"regexp">a{
3,
5}?
</tt> will only match
3
<DT><STRONG>"<tt class="character
">\</tt>"</STRONG></DT>
<DD>Either escapes special characters (permitting
you to match characters like
"<tt class="character
">*</tt>",
"<tt class="character
">?</tt>", and so
forth), or signals a special sequence; special sequences are discussed
If you're not using a raw string to
express the pattern, remember that Python also uses the
backslash as an escape sequence in string literals; if the escape
sequence isn't recognized by Python's parser, the backslash and
subsequent character are included in the resulting string. However,
if Python would recognize the resulting sequence, the backslash should
be repeated twice. This is complicated and hard to understand, so
it's highly recommended that you use raw strings for all but the
<DT><STRONG><code>[]
</code></STRONG></DT>
<DD>Used to indicate a set of characters. Characters can
be listed individually, or a range of characters can be indicated by
giving two characters and separating them by a
"<tt class="character
">-</tt>". Special
characters are not active inside sets. For example,
<tt class=
"regexp">[akm$]
</tt>will match any of the characters
"<tt class="character
">a</tt>",
"<tt class="character
">k</tt>",
"<tt class="character
">m</tt>", or
"<tt class="character
">$</tt>";
<tt class=
"regexp">[a-z]
</tt>
will match any lowercase letter, and
<code>[a-zA-Z0-
9]
</code> matches any
letter or digit. Character classes such as
<code>\w
</code> or
<code>\S
</code>(defined below) are also acceptable inside a range. If you want to
include a
"<tt class="character
">]</tt>" or a
"<tt class="character
">-</tt>" inside a set, precede it with a
backslash, or place it as the first character. The
pattern
<tt class=
"regexp">[]]
</tt> will match
<code>']'
</code>, for example.
You can match the characters not within a range by
<i class=
"dfn">complementing
</i>the set. This is indicated by including a
"<tt class="character
">^</tt>" as the first character of the set;
"<tt class="character
">^</tt>" elsewhere will simply match the
"<tt class="character
">^</tt>" character. For example,
<tt class=
"regexp">[^
5]
</tt> will match
any character except
"<tt class="character
">5</tt>", and
<tt class=
"regexp">[^
<code>^
</code>]
</tt> will match any character
except
"<tt class="character
">^</tt>".
<DT><STRONG>"<tt class="character
">|</tt>"</STRONG></DT>
<DD><code>A|B
</code>, where A and B can be arbitrary REs,
creates a regular expression that will match either A or B. An
arbitrary number of REs can be separated by the
"<tt class="character
">|</tt>" in this
way. This can be used inside groups (see below) as well. As the target
string is scanned, REs separated by
"<tt class="character
">|</tt>" are tried from left to
right. When one pattern completely matches, that branch is accepted.
This means that once
<code>A
</code> matches,
<code>B
</code> will not be tested further,
even if it would produce a longer overall match. In other words, the
"<tt class="character
">|</tt>" operator is never greedy. To match a literal
"<tt class="character
">|</tt>",
use
<tt class=
"regexp">\|
</tt>, or enclose it inside a character class, as in
<tt class=
"regexp">[|]
</tt>.
<DT><STRONG><code>(...)
</code></STRONG></DT>
<DD>Matches whatever regular expression is inside the
parentheses, and indicates the start and end of a group; the contents
of a group can be retrieved after a match has been performed, and can
be matched later in the string with the
<tt class=
"regexp">\<var>number
</var></tt> special
sequence, described below. To match the literals
"<tt class="character
">(</tt>" or
"<tt class="character
">)</tt>", use
<tt class=
"regexp">\(
</tt> or
<tt class=
"regexp">\)
</tt>, or enclose them
inside a character class:
<tt class=
"regexp">[(] [)]
</tt>.
<DT><STRONG><code>(?...)
</code></STRONG></DT>
<DD>This is an extension notation (a
"<tt class="character
">?</tt>"
following a
"<tt class="character
">(</tt>" is not meaningful otherwise). The first
character after the
"<tt class="character
">?</tt>"determines what the meaning and further syntax of the construct is.
Extensions usually do not create a new group;
<tt class=
"regexp">(?P
<<var>name
</var>>...)
</tt> is the only exception to this rule.
Following are the currently supported extensions.
<DT><STRONG><code>(?iLmsux)
</code></STRONG></DT>
<DD>(One or more letters from the set
"<tt class="character
">i</tt>",
"<tt class="character
">L</tt>",
"<tt class="character
">m</tt>",
"<tt class="character
">s</tt>",
"<tt class="character
">u</tt>",
"<tt class="character
">x</tt>".) The group matches the empty string; the letters set
the corresponding flags (
<tt class=
"constant">re.I
</tt>,
<tt class=
"constant">re.L
</tt>,
<tt class=
"constant">re.M
</tt>,
<tt class=
"constant">re.S
</tt>,
<tt class=
"constant">re.U
</tt>,
<tt class=
"constant">re.X
</tt>)
for the entire regular expression. This is useful if you wish to
include the flags as part of the regular expression, instead of
passing a
<var>flag
</var> argument to the
<tt class=
"function">compile()
</tt> function.
Note that the
<tt class=
"regexp">(?x)
</tt> flag changes how the expression is parsed.
It should be used first in the expression string, or after one or more
whitespace characters. If there are non-whitespace characters before
the flag, the results are undefined.
<DT><STRONG><code>(?:...)
</code></STRONG></DT>
<DD>A non-grouping version of regular parentheses.
Matches whatever regular expression is inside the parentheses, but the
group
<em>cannot
</em> be retrieved after performing a match or
referenced later in the pattern.
<DT><STRONG><code>(?P
<<var>name
</var>>...)
</code></STRONG></DT>
<DD>Similar to regular parentheses, but
the substring matched by the group is accessible via the symbolic group
name
<var>name
</var>. Group names must be valid Python identifiers, and
each group name must be defined only once within a regular expression. A
symbolic group is also a numbered group, just as if the group were not
named. So the group named 'id' in the example above can also be
referenced as the numbered group
1.
For example, if the pattern is
<tt class=
"regexp">(?P
<id
>[a-zA-Z_]
\w*)
</tt>, the group can be referenced by its
name in arguments to methods of match objects, such as
<code>m.group('id')
</code> or
<code>m.end('id')
</code>, and also by name in
pattern text (for example,
<tt class=
"regexp">(?P=id)
</tt>) and replacement text
(such as
<code>\g
<id
></code>).
<DT><STRONG><code>(?P=
<var>name
</var>)
</code></STRONG></DT>
<DD>Matches whatever text was matched by the
earlier group named
<var>name
</var>.
<DT><STRONG><code>(?#...)
</code></STRONG></DT>
<DD>A comment; the contents of the parentheses are
<DT><STRONG><code>(?=...)
</code></STRONG></DT>
<DD>Matches if
<tt class=
"regexp">...
</tt> matches next, but doesn't
consume any of the string. This is called a lookahead assertion. For
example,
<tt class=
"regexp">Isaac (?=Asimov)
</tt> will match
<code>'Isaac
'
</code> only if it's
followed by
<code>'Asimov'
</code>.
<DT><STRONG><code>(?!...)
</code></STRONG></DT>
<DD>Matches if
<tt class=
"regexp">...
</tt> doesn't match next. This
is a negative lookahead assertion. For example,
<tt class=
"regexp">Isaac (?!Asimov)
</tt> will match
<code>'Isaac
'
</code> only if it's
<em>not
</em>
followed by
<code>'Asimov'
</code>.
<DT><STRONG><code>(?
<=...)
</code></STRONG></DT>
<DD>Matches if the current position in the string
is preceded by a match for
<tt class=
"regexp">...
</tt> that ends at the current
position. This is called a
<i class=
"dfn">positive lookbehind assertion
</i>.
<tt class=
"regexp">(?
<=abc)def
</tt> will find a match in
"<tt class="samp
">abcdef</tt>", since the
lookbehind will back up
3 characters and check if the contained
pattern matches. The contained pattern must only match strings of
some fixed length, meaning that
<tt class=
"regexp">abc
</tt> or
<tt class=
"regexp">a|b
</tt> are
allowed, but
<tt class=
"regexp">a*
</tt> and
<tt class=
"regexp">a{
3,
4}
</tt> are not. Note that
patterns which start with positive lookbehind assertions will never
match at the beginning of the string being searched; you will most
likely want to use the
<tt class=
"function">search()
</tt> function rather than the
<tt class=
"function">match()
</tt> function:
<div class=
"verbatim"><pre>
>>> m = re.search('(?
<=abc)def', 'abcdef')
This example looks for a word following a hyphen:
<div class=
"verbatim"><pre>
>>> m = re.search('(?
<=-)\w+', 'spam-egg')
<DT><STRONG><code>(?
<!...)
</code></STRONG></DT>
<DD>Matches if the current position in the string
is not preceded by a match for
<tt class=
"regexp">...
</tt>. This is called a
<i class=
"dfn">negative lookbehind assertion
</i>. Similar to positive lookbehind
assertions, the contained pattern must only match strings of some
fixed length. Patterns which start with negative lookbehind
assertions may match at the beginning of the string being searched.
<DT><STRONG><code>(?(
<var>id/name
</var>)yes-pattern|no-pattern)
</code></STRONG></DT>
with
<tt class=
"regexp">yes-pattern
</tt> if the group with given
<var>id
</var> or
<var>name
</var>exists, and with
<tt class=
"regexp">no-pattern
</tt> if it doesn't.
<tt class=
"regexp">|no-pattern
</tt>is optional and can be omitted. For example,
<tt class=
"regexp">(
<)?(
\w+@
\w+(?:
\.
\w+)+)(?(
1)
>)
</tt> is a poor email matching
pattern, which will match with
<code>'
<user@host.com
>'
</code> as well as
<code>'user@host.com'
</code>, but not with
<code>'
<user@host.com'
</code>.
<span class=
"versionnote">New in version
2.4.
</span>
The special sequences consist of
"<tt class="character
">\</tt>" and a character from the
list below. If the ordinary character is not on the list, then the
resulting RE will match the second character. For example,
<tt class=
"regexp">\$
</tt> matches the character
"<tt class="character
">$</tt>".
<DT><STRONG><code>\<var>number
</var></code></STRONG></DT>
<DD>Matches the contents of the group of the
same number. Groups are numbered starting from
1. For example,
<tt class=
"regexp">(.+)
\1</tt> matches
<code>'the the'
</code> or
<code>'
55 55'
</code>, but not
<code>'the end'
</code> (note
the space after the group). This special sequence can only be used to
match one of the first
99 groups. If the first digit of
<var>number
</var>is
0, or
<var>number
</var> is
3 octal digits long, it will not be interpreted
as a group match, but as the character with octal value
<var>number
</var>.
Inside the
"<tt class="character
">[</tt>" and
"<tt class="character
">]</tt>" of a character class, all numeric
escapes are treated as characters.
<DT><STRONG><code>\A
</code></STRONG></DT>
<DD>Matches only at the start of the string.
<DT><STRONG><code>\b
</code></STRONG></DT>
<DD>Matches the empty string, but only at the
beginning or end of a word. A word is defined as a sequence of
alphanumeric or underscore characters, so the end of a word is indicated by
whitespace or a non-alphanumeric, non-underscore character. Note that
<code>\b
</code> is defined as the boundary between
<code>\w
</code> and
<code>\
W
</code>, so the precise set of characters deemed to be alphanumeric depends on the
values of the
<code>UNICODE
</code> and
<code>LOCALE
</code> flags. Inside a character
range,
<tt class=
"regexp">\b
</tt> represents the backspace character, for compatibility
with Python's string literals.
<DT><STRONG><code>\B
</code></STRONG></DT>
<DD>Matches the empty string, but only when it is
<em>not
</em>
at the beginning or end of a word. This is just the opposite of
<code>\b
</code>, so is also subject to the settings of
<code>LOCALE
</code> and
<code>UNICODE
</code>.
<DT><STRONG><code>\d
</code></STRONG></DT>
<DD>When the
<tt class=
"constant">UNICODE
</tt> flag is not specified, matches
any decimal digit; this is equivalent to the set
<tt class=
"regexp">[
0-
9]
</tt>.
With
<tt class=
"constant">UNICODE
</tt>, it will match whatever is classified as a digit
in the Unicode character properties database.
<DT><STRONG><code>\D
</code></STRONG></DT>
<DD>When the
<tt class=
"constant">UNICODE
</tt> flag is not specified, matches
any non-digit character; this is equivalent to the set
<tt class=
"regexp">[^
0-
9]
</tt>. With
<tt class=
"constant">UNICODE
</tt>, it will match
anything other than character marked as digits in the Unicode character
<DT><STRONG><code>\s
</code></STRONG></DT>
<DD>When the
<tt class=
"constant">LOCALE
</tt> and
<tt class=
"constant">UNICODE
</tt>
flags are not specified, matches any whitespace character; this is
equivalent to the set
<tt class=
"regexp">[
\t
\n
\r
\f
\v]
</tt>.
With
<tt class=
"constant">LOCALE
</tt>, it will match this set plus whatever characters
are defined as space for the current locale. If
<tt class=
"constant">UNICODE
</tt> is set,
this will match the characters
<tt class=
"regexp">[
\t
\n
\r
\f
\v]
</tt> plus
whatever is classified as space in the Unicode character properties
<DT><STRONG><code>\S
</code></STRONG></DT>
<DD>When the
<tt class=
"constant">LOCALE
</tt> and
<tt class=
"constant">UNICODE
</tt>
flags are not specified, matches any non-whitespace character; this is
equivalent to the set
<tt class=
"regexp">[^
\t
\n
\r
\f
\v]
</tt>With
<tt class=
"constant">LOCALE
</tt>, it will match any character not in this set,
and not defined as space in the current locale. If
<tt class=
"constant">UNICODE
</tt>is set, this will match anything other than
<tt class=
"regexp">[
\t
\n
\r
\f
\v]
</tt>and characters marked as space in the Unicode character properties database.
<DT><STRONG><code>\w
</code></STRONG></DT>
<DD>When the
<tt class=
"constant">LOCALE
</tt> and
<tt class=
"constant">UNICODE
</tt>
flags are not specified, matches any alphanumeric character and the
underscore; this is equivalent to the set
<tt class=
"regexp">[a-zA-Z0-
9_]
</tt>. With
<tt class=
"constant">LOCALE
</tt>, it will match the set
<tt class=
"regexp">[
0-
9_]
</tt> plus whatever characters are defined as alphanumeric for
the current locale. If
<tt class=
"constant">UNICODE
</tt> is set, this will match the
characters
<tt class=
"regexp">[
0-
9_]
</tt> plus whatever is classified as alphanumeric
in the Unicode character properties database.
<DT><STRONG><code>\W
</code></STRONG></DT>
<DD>When the
<tt class=
"constant">LOCALE
</tt> and
<tt class=
"constant">UNICODE
</tt>
flags are not specified, matches any non-alphanumeric character; this
is equivalent to the set
<tt class=
"regexp">[^a-zA-Z0-
9_]
</tt>. With
<tt class=
"constant">LOCALE
</tt>, it will match any character not in the set
<tt class=
"regexp">[
0-
9_]
</tt>, and not defined as alphanumeric for the current locale.
If
<tt class=
"constant">UNICODE
</tt> is set, this will match anything other than
<tt class=
"regexp">[
0-
9_]
</tt> and characters marked as alphanumeric in the Unicode
character properties database.
<DT><STRONG><code>\Z
</code></STRONG></DT>
<DD>Matches only at the end of the string.
Most of the standard escapes supported by Python string literals are
also accepted by the regular expression parser:
<div class=
"verbatim"><pre>
Octal escapes are included in a limited form: If the first digit is a
0, or if there are three octal digits, it is considered an octal
escape. Otherwise, it is a group reference. As for string literals,
octal escapes are always at most three digits in length.
<div class='online-navigation'
>
<table align=
"center" width=
"100%" cellpadding=
"0" cellspacing=
"2">
<td class='online-navigation'
><a rel=
"prev" title=
"4.2 re "
href=
"module-re.html"><img src='../icons/previous.png'
border='
0' height='
32' alt='Previous Page' width='
32'
/></A></td><td class='online-navigation'
><a rel=
"parent" title=
"4.2 re "
href=
"module-re.html"><img src='../icons/up.png'
border='
0' height='
32' alt='Up One Level' width='
32'
/></A></td><td class='online-navigation'
><a rel=
"next" title=
"4.2.2 Matching vs Searching"
href=
"matching-searching.html"><img src='../icons/next.png'
border='
0' height='
32' alt='Next Page' width='
32'
/></A></td><td align=
"center" width=
"100%">Python Library Reference
</td>
<td class='online-navigation'
><a rel=
"contents" title=
"Table of Contents"
href=
"contents.html"><img src='../icons/contents.png'
border='
0' height='
32' alt='Contents' width='
32'
/></A></td><td class='online-navigation'
><a href=
"modindex.html" title=
"Module Index"><img src='../icons/modules.png'
border='
0' height='
32' alt='Module Index' width='
32'
/></a></td><td class='online-navigation'
><a rel=
"index" title=
"Index"
href=
"genindex.html"><img src='../icons/index.png'
border='
0' height='
32' alt='Index' width='
32'
/></A></td><div class='online-navigation'
>
<b class=
"navlabel">Previous:
</b>
<a class=
"sectref" rel=
"prev" href=
"module-re.html">4.2 re
</A>
<b class=
"navlabel">Up:
</b>
<a class=
"sectref" rel=
"parent" href=
"module-re.html">4.2 re
</A>
<b class=
"navlabel">Next:
</b>
<a class=
"sectref" rel=
"next" href=
"matching-searching.html">4.2.2 Matching vs Searching
</A>
<span class=
"release-info">Release
2.4.2, documentation updated on
28 September
2005.
</span>
<!--End of Navigation Panel-->
See
<i><a href=
"about.html">About this document...
</a></i> for information on suggesting changes.
projects / OpenSPARC-T2-SAM / blob