ref2.tex 26.2 KB
Newer Older
1
\chapter{Lexical analysis\label{lexical}}
2

3 4
A Python program is read by a \emph{parser}.  Input to the parser is a
stream of \emph{tokens}, generated by the \emph{lexical analyzer}.  This
5 6 7 8 9
chapter describes how the lexical analyzer breaks a file into tokens.
\index{lexical analysis}
\index{parser}
\index{token}

10 11 12 13 14 15 16 17
Python uses the 7-bit \ASCII{} character set for program text.
\versionadded[An encoding declaration can be used to indicate that 
string literals and comments use an encoding different from ASCII.]{2.3}
For compatibility with older versions, Python only warns if it finds
8-bit characters; those warnings should be corrected by either declaring
an explicit encoding, or using escape sequences if those bytes are binary
data, instead of characters.

18 19

The run-time character set depends on the I/O devices connected to the
20
program but is generally a superset of \ASCII.
21 22 23 24 25 26 27 28 29 30 31 32 33

\strong{Future compatibility note:} It may be tempting to assume that the
character set for 8-bit characters is ISO Latin-1 (an \ASCII{}
superset that covers most western languages that use the Latin
alphabet), but it is possible that in the future Unicode text editors
will become common.  These generally use the UTF-8 encoding, which is
also an \ASCII{} superset, but with very different use for the
characters with ordinals 128-255.  While there is no consensus on this
subject yet, it is unwise to assume either Latin-1 or UTF-8, even
though the current implementation appears to favor Latin-1.  This
applies both to the source character set and the run-time character
set.

34

35
\section{Line structure\label{line-structure}}
36

37 38 39
A Python program is divided into a number of \emph{logical lines}.
\index{line structure}

40

41
\subsection{Logical lines\label{logical}}
42 43

The end of
44 45
a logical line is represented by the token NEWLINE.  Statements cannot
cross logical line boundaries except where NEWLINE is allowed by the
Guido van Rossum's avatar
Guido van Rossum committed
46
syntax (e.g., between statements in compound statements).
47 48
A logical line is constructed from one or more \emph{physical lines}
by following the explicit or implicit \emph{line joining} rules.
49
\index{logical line}
50 51
\index{physical line}
\index{line joining}
52 53
\index{NEWLINE token}

54

55
\subsection{Physical lines\label{physical}}
56 57

A physical line ends in whatever the current platform's convention is
58
for terminating lines.  On \UNIX, this is the \ASCII{} LF (linefeed)
59
character.  On Windows, it is the \ASCII{} sequence CR LF (return
60 61 62
followed by linefeed).  On Macintosh, it is the \ASCII{} CR (return)
character.

63

64
\subsection{Comments\label{comments}}
65

66
A comment starts with a hash character (\code{\#}) that is not part of
67
a string literal, and ends at the end of the physical line.  A comment
68 69 70
signifies the end of the logical line unless the implicit line joining
rules are invoked.
Comments are ignored by the syntax; they are not tokens.
71 72 73
\index{comment}
\index{hash character}

74

75 76 77
\subsection{Encoding declarations\label{encodings}}

If a comment in the first or second line of the Python script matches
78
the regular expression \regexp{coding[=:]\e s*([\e w-_.]+)}, this comment is
79 80 81 82 83 84 85 86 87 88 89 90 91 92 93
processed as an encoding declaration; the first group of this
expression names the encoding of the source code file. The recommended
forms of this expression are

\begin{verbatim}
# -*- coding: <encoding-name> -*-
\end{verbatim}

which is recognized also by GNU Emacs, and

\begin{verbatim}
# vim:fileencoding=<encoding-name>
\end{verbatim}

which is recognized by Bram Moolenar's VIM. In addition, if the first
94 95 96
bytes of the file are the UTF-8 byte-order mark
(\code{'\e xef\e xbb\e xbf'}), the declared file encoding is UTF-8
(this is supported, among others, by Microsoft's \program{notepad}).
97 98 99 100 101 102 103

If an encoding is declared, the encoding name must be recognized by
Python. % XXX there should be a list of supported encodings.
The encoding is used for all lexical analysis, in particular to find
the end of a string, and to interpret the contents of Unicode literals.
String literals are converted to Unicode for syntactical analysis,
then converted back to their original encoding before interpretation
104
starts. The encoding declaration must appear on a line of its own.
105

106
\subsection{Explicit line joining\label{explicit-joining}}
107 108

Two or more physical lines may be joined into logical lines using
109
backslash characters (\code{\e}), as follows: when a physical line ends
110 111 112 113 114 115 116 117 118 119 120 121 122 123 124
in a backslash that is not part of a string literal or comment, it is
joined with the following forming a single logical line, deleting the
backslash and the following end-of-line character.  For example:
\index{physical line}
\index{line joining}
\index{line continuation}
\index{backslash character}
%
\begin{verbatim}
if 1900 < year < 2100 and 1 <= month <= 12 \
   and 1 <= day <= 31 and 0 <= hour < 24 \
   and 0 <= minute < 60 and 0 <= second < 60:   # Looks like a valid date
        return 1
\end{verbatim}

125 126 127 128 129
A line ending in a backslash cannot carry a comment.  A backslash does
not continue a comment.  A backslash does not continue a token except
for string literals (i.e., tokens other than string literals cannot be
split across physical lines using a backslash).  A backslash is
illegal elsewhere on a line outside a string literal.
130

131

132
\subsection{Implicit line joining\label{implicit-joining}}
133 134 135 136 137 138 139 140 141 142 143 144 145 146

Expressions in parentheses, square brackets or curly braces can be
split over more than one physical line without using backslashes.
For example:

\begin{verbatim}
month_names = ['Januari', 'Februari', 'Maart',      # These are the
               'April',   'Mei',      'Juni',       # Dutch names
               'Juli',    'Augustus', 'September',  # for the months
               'Oktober', 'November', 'December']   # of the year
\end{verbatim}

Implicitly continued lines can carry comments.  The indentation of the
continuation lines is not important.  Blank continuation lines are
147 148 149
allowed.  There is no NEWLINE token between implicit continuation
lines.  Implicitly continued lines can also occur within triple-quoted
strings (see below); in that case they cannot carry comments.
150 151


152
\subsection{Blank lines \label{blank-lines}}
153

154
\index{blank line}
155 156 157 158 159 160 161 162
A logical line that contains only spaces, tabs, formfeeds and possibly
a comment, is ignored (i.e., no NEWLINE token is generated).  During
interactive input of statements, handling of a blank line may differ
depending on the implementation of the read-eval-print loop.  In the
standard implementation, an entirely blank logical line (i.e.\ one
containing not even whitespace or a comment) terminates a multi-line
statement.

163

164
\subsection{Indentation\label{indentation}}
165 166 167 168 169 170 171 172 173 174 175 176 177

Leading whitespace (spaces and tabs) at the beginning of a logical
line is used to compute the indentation level of the line, which in
turn is used to determine the grouping of statements.
\index{indentation}
\index{whitespace}
\index{leading whitespace}
\index{space}
\index{tab}
\index{grouping}
\index{statement grouping}

First, tabs are replaced (from left to right) by one to eight spaces
178 179
such that the total number of characters up to and including the
replacement is a multiple of
180
eight (this is intended to be the same rule as used by \UNIX).  The
181 182
total number of spaces preceding the first non-blank character then
determines the line's indentation.  Indentation cannot be split over
183 184 185 186 187 188 189 190
multiple physical lines using backslashes; the whitespace up to the
first backslash determines the indentation.

\strong{Cross-platform compatibility note:} because of the nature of
text editors on non-UNIX platforms, it is unwise to use a mixture of
spaces and tabs for the indentation in a single source file.

A formfeed character may be present at the start of the line; it will
191
be ignored for the indentation calculations above.  Formfeed
192 193 194
characters occurring elsewhere in the leading whitespace have an
undefined effect (for instance, they may reset the space count to
zero).
195 196 197 198 199 200 201 202 203 204 205 206

The indentation levels of consecutive lines are used to generate
INDENT and DEDENT tokens, using a stack, as follows.
\index{INDENT token}
\index{DEDENT token}

Before the first line of the file is read, a single zero is pushed on
the stack; this will never be popped off again.  The numbers pushed on
the stack will always be strictly increasing from bottom to top.  At
the beginning of each logical line, the line's indentation level is
compared to the top of the stack.  If it is equal, nothing happens.
If it is larger, it is pushed on the stack, and one INDENT token is
207
generated.  If it is smaller, it \emph{must} be one of the numbers
208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232
occurring on the stack; all numbers on the stack that are larger are
popped off, and for each number popped off a DEDENT token is
generated.  At the end of the file, a DEDENT token is generated for
each number remaining on the stack that is larger than zero.

Here is an example of a correctly (though confusingly) indented piece
of Python code:

\begin{verbatim}
def perm(l):
        # Compute the list of all permutations of l
    if len(l) <= 1:
                  return [l]
    r = []
    for i in range(len(l)):
             s = l[:i] + l[i+1:]
             p = perm(s)
             for x in p:
              r.append(l[i:i+1] + x)
    return r
\end{verbatim}

The following example shows various indentation errors:

\begin{verbatim}
233 234 235 236 237 238 239
 def perm(l):                       # error: first line indented
for i in range(len(l)):             # error: not indented
    s = l[:i] + l[i+1:]
        p = perm(l[:i] + l[i+1:])   # error: unexpected indent
        for x in p:
                r.append(l[i:i+1] + x)
            return r                # error: inconsistent dedent
240 241 242 243
\end{verbatim}

(Actually, the first three errors are detected by the parser; only the
last error is found by the lexical analyzer --- the indentation of
244
\code{return r} does not match a level popped off the stack.)
245

246

247
\subsection{Whitespace between tokens\label{whitespace}}
248 249 250 251 252 253 254

Except at the beginning of a logical line or in string literals, the
whitespace characters space, tab and formfeed can be used
interchangeably to separate tokens.  Whitespace is needed between two
tokens only if their concatenation could otherwise be interpreted as a
different token (e.g., ab is one token, but a b is two tokens).

255

256
\section{Other tokens\label{other-tokens}}
257 258

Besides NEWLINE, INDENT and DEDENT, the following categories of tokens
259 260 261 262 263
exist: \emph{identifiers}, \emph{keywords}, \emph{literals},
\emph{operators}, and \emph{delimiters}.
Whitespace characters (other than line terminators, discussed earlier)
are not tokens, but serve to delimit tokens.
Where
264 265 266
ambiguity exists, a token comprises the longest possible string that
forms a legal token, when read from left to right.

267

268
\section{Identifiers and keywords\label{identifiers}}
269

270
Identifiers (also referred to as \emph{names}) are described by the following
271 272 273 274
lexical definitions:
\index{identifier}
\index{name}

275 276 277 278 279 280 281 282 283 284 285 286
\begin{productionlist}
  \production{identifier}
             {(\token{letter}|"_") (\token{letter} | \token{digit} | "_")*}
  \production{letter}
             {\token{lowercase} | \token{uppercase}}
  \production{lowercase}
             {"a"..."z"}
  \production{uppercase}
             {"A"..."Z"}
  \production{digit}
             {"0"..."9"}
\end{productionlist}
287 288 289

Identifiers are unlimited in length.  Case is significant.

290

291
\subsection{Keywords\label{keywords}}
292

293 294 295 296
The following identifiers are used as reserved words, or
\emph{keywords} of the language, and cannot be used as ordinary
identifiers.  They must be spelled exactly as written here:%
\index{keyword}%
297 298 299
\index{reserved word}

\begin{verbatim}
300 301 302
and       del       for       is        raise    
assert    elif      from      lambda    return   
break     else      global    not       try      
303 304
class     except    if        or        while    
continue  exec      import    pass      yield    
305
def       finally   in        print              
306 307
\end{verbatim}

308 309
% When adding keywords, use reswords.py for reformatting

310 311 312 313 314 315 316
Note that although the identifier \code{as} can be used as part of the
syntax of \keyword{import} statements, it is not currently a reserved
word.

In some future version of Python, the identifiers \code{as} and
\code{None} will both become keywords.

317

318
\subsection{Reserved classes of identifiers\label{id-classes}}
319 320 321 322

Certain classes of identifiers (besides keywords) have special
meanings.  These are:

323 324 325 326 327
\begin{tableiii}{l|l|l}{code}{Form}{Meaning}{Notes}
\lineiii{_*}{Not imported by \samp{from \var{module} import *}}{(1)}
\lineiii{__*__}{System-defined name}{}
\lineiii{__*}{Class-private name mangling}{}
\end{tableiii}
328

329 330 331
See sections: \ref{import}, ``The \keyword{import} statement'';
\ref{specialnames}, ``Special method names'';
\ref{atom-identifiers}, ``Identifiers (Names)''.
332

333 334 335 336 337 338 339 340 341 342
Note:

\begin{description}
\item[(1)] The special identifier \samp{_} is used in the interactive
interpreter to store the result of the last evaluation; it is stored
in the \module{__builtin__} module.  When not in interactive mode,
\samp{_} has no special meaning and is not defined.
\end{description}


343
\section{Literals\label{literals}}
344 345 346 347 348

Literals are notations for constant values of some built-in types.
\index{literal}
\index{constant}

349

350
\subsection{String literals\label{strings}}
351 352 353 354

String literals are described by the following lexical definitions:
\index{string literal}

355
\index{ASCII@\ASCII}
356 357
\begin{productionlist}
  \production{stringliteral}
358 359 360
             {[\token{stringprefix}](\token{shortstring} | \token{longstring})}
  \production{stringprefix}
             {"r" | "u" | "ur" | "R" | "U" | "UR" | "Ur" | "uR"}
361 362 363 364
  \production{shortstring}
             {"'" \token{shortstringitem}* "'"
              | '"' \token{shortstringitem}* '"'}
  \production{longstring}
365 366
             {"'''" \token{longstringitem}* "'''"}
  \productioncont{| '"""' \token{longstringitem}* '"""'}
367 368 369 370 371 372 373
  \production{shortstringitem}
             {\token{shortstringchar} | \token{escapeseq}}
  \production{longstringitem}
             {\token{longstringchar} | \token{escapeseq}}
  \production{shortstringchar}
             {<any ASCII character except "\e" or newline or the quote>}
  \production{longstringchar}
374
             {<any ASCII character except "\e">}
375 376 377
  \production{escapeseq}
             {"\e" <any ASCII character>}
\end{productionlist}
378

379 380 381 382
One syntactic restriction not indicated by these productions is that
whitespace is not allowed between the \grammartoken{stringprefix} and
the rest of the string literal.

383 384 385
\index{triple-quoted string}
\index{Unicode Consortium}
\index{string!Unicode}
386 387 388 389 390 391 392
In plain English: String literals can be enclosed in matching single
quotes (\code{'}) or double quotes (\code{"}).  They can also be
enclosed in matching groups of three single or double quotes (these
are generally referred to as \emph{triple-quoted strings}).  The
backslash (\code{\e}) character is used to escape characters that
otherwise have a special meaning, such as newline, backslash itself,
or the quote character.  String literals may optionally be prefixed
393 394 395 396 397
with a letter \character{r} or \character{R}; such strings are called
\dfn{raw strings}\index{raw string} and use different rules for interpreting
backslash escape sequences.  A prefix of \character{u} or \character{U}
makes the string a Unicode string.  Unicode strings use the Unicode character
set as defined by the Unicode Consortium and ISO~10646.  Some additional
398
escape sequences, described below, are available in Unicode strings.
399 400
The two prefix characters may be combined; in this case, \character{u} must
appear before \character{r}.
401 402

In triple-quoted strings,
403 404 405
unescaped newlines and quotes are allowed (and are retained), except
that three unescaped quotes in a row terminate the string.  (A
``quote'' is the character used to open the string, i.e. either
406
\code{'} or \code{"}.)
407

408 409
Unless an \character{r} or \character{R} prefix is present, escape
sequences in strings are interpreted according to rules similar
410
to those used by Standard C.  The recognized escape sequences are:
411 412 413 414 415
\index{physical line}
\index{escape sequence}
\index{Standard C}
\index{C}

416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436
\begin{tableiii}{l|l|c}{code}{Escape Sequence}{Meaning}{Notes}
\lineiii{\e\var{newline}} {Ignored}{}
\lineiii{\e\e}	{Backslash (\code{\e})}{}
\lineiii{\e'}	{Single quote (\code{'})}{}
\lineiii{\e"}	{Double quote (\code{"})}{}
\lineiii{\e a}	{\ASCII{} Bell (BEL)}{}
\lineiii{\e b}	{\ASCII{} Backspace (BS)}{}
\lineiii{\e f}	{\ASCII{} Formfeed (FF)}{}
\lineiii{\e n}	{\ASCII{} Linefeed (LF)}{}
\lineiii{\e N\{\var{name}\}}
        {Character named \var{name} in the Unicode database (Unicode only)}{}
\lineiii{\e r}	{\ASCII{} Carriage Return (CR)}{}
\lineiii{\e t}	{\ASCII{} Horizontal Tab (TAB)}{}
\lineiii{\e u\var{xxxx}}
        {Character with 16-bit hex value \var{xxxx} (Unicode only)}{(1)}
\lineiii{\e U\var{xxxxxxxx}}
        {Character with 32-bit hex value \var{xxxxxxxx} (Unicode only)}{(2)}
\lineiii{\e v}	{\ASCII{} Vertical Tab (VT)}{}
\lineiii{\e\var{ooo}} {\ASCII{} character with octal value \var{ooo}}{(3)}
\lineiii{\e x\var{hh}} {\ASCII{} character with hex value \var{hh}}{(4)}
\end{tableiii}
437
\index{ASCII@\ASCII}
438

439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457
\noindent
Notes:

\begin{itemize}
\item[(1)]
  Individual code units which form parts of a surrogate pair can be
  encoded using this escape sequence.
\item[(2)]
  Any Unicode character can be encoded this way, but characters
  outside the Basic Multilingual Plane (BMP) will be encoded using a
  surrogate pair if Python is compiled to use 16-bit code units (the
  default).  Individual code units which form parts of a surrogate
  pair can be encoded using this escape sequence.
\item[(3)]
  As in Standard C, up to three octal digits are accepted.
\item[(4)]
  Unlike in Standard C, at most two hex digits are accepted.
\end{itemize}

458

459
Unlike Standard \index{unrecognized escape sequence}C,
460
all unrecognized escape sequences are left in the string unchanged,
461
i.e., \emph{the backslash is left in the string}.  (This behavior is
462
useful when debugging: if an escape sequence is mistyped, the
463 464 465 466
resulting output is more easily recognized as broken.)  It is also
important to note that the escape sequences marked as ``(Unicode
only)'' in the table above fall into the category of unrecognized
escapes for non-Unicode string literals.
467

468 469
When an \character{r} or \character{R} prefix is present, a character
following a backslash is included in the string without change, and \emph{all
470 471
backslashes are left in the string}.  For example, the string literal
\code{r"\e n"} consists of two characters: a backslash and a lowercase
472 473
\character{n}.  String quotes can be escaped with a backslash, but the
backslash remains in the string; for example, \code{r"\e""} is a valid string
474
literal consisting of two characters: a backslash and a double quote;
475
\code{r"\e"} is not a valid string literal (even a raw string cannot
476 477 478 479 480
end in an odd number of backslashes).  Specifically, \emph{a raw
string cannot end in a single backslash} (since the backslash would
escape the following quote character).  Note also that a single
backslash followed by a newline is interpreted as those two characters
as part of the string, \emph{not} as a line continuation.
481

482 483 484
When an \character{r} or \character{R} prefix is used in conjunction
with a \character{u} or \character{U} prefix, then the \code{\e uXXXX}
escape sequence is processed while \emph{all other backslashes are
485 486 487 488 489 490
left in the string}.  For example, the string literal
\code{ur"\e{}u0062\e n"} consists of three Unicode characters: `LATIN
SMALL LETTER B', `REVERSE SOLIDUS', and `LATIN SMALL LETTER N'.
Backslashes can be escaped with a preceding backslash; however, both
remain in the string.  As a result, \code{\e uXXXX} escape sequences
are only recognized when there are an odd number of backslashes.
491

492
\subsection{String literal concatenation\label{string-catenation}}
493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513

Multiple adjacent string literals (delimited by whitespace), possibly
using different quoting conventions, are allowed, and their meaning is
the same as their concatenation.  Thus, \code{"hello" 'world'} is
equivalent to \code{"helloworld"}.  This feature can be used to reduce
the number of backslashes needed, to split long strings conveniently
across long lines, or even to add comments to parts of strings, for
example:

\begin{verbatim}
re.compile("[A-Za-z_]"       # letter or underscore
           "[A-Za-z0-9_]*"   # letter, digit or underscore
          )
\end{verbatim}

Note that this feature is defined at the syntactical level, but
implemented at compile time.  The `+' operator must be used to
concatenate string expressions at run time.  Also note that literal
concatenation can use different quoting styles for each component
(even mixing raw strings and triple quoted strings).

514

515
\subsection{Numeric literals\label{numbers}}
516

517 518 519 520
There are four types of numeric literals: plain integers, long
integers, floating point numbers, and imaginary numbers.  There are no
complex literals (complex numbers can be formed by adding a real
number and an imaginary number).
521 522 523 524 525 526 527 528 529
\index{number}
\index{numeric literal}
\index{integer literal}
\index{plain integer literal}
\index{long integer literal}
\index{floating point literal}
\index{hexadecimal literal}
\index{octal literal}
\index{decimal literal}
530
\index{imaginary literal}
531
\index{complex!literal}
532 533 534 535 536

Note that numeric literals do not include a sign; a phrase like
\code{-1} is actually an expression composed of the unary operator
`\code{-}' and the literal \code{1}.

537

538
\subsection{Integer and long integer literals\label{integers}}
539 540 541 542

Integer and long integer literals are described by the following
lexical definitions:

543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560
\begin{productionlist}
  \production{longinteger}
             {\token{integer} ("l" | "L")}
  \production{integer}
             {\token{decimalinteger} | \token{octinteger} | \token{hexinteger}}
  \production{decimalinteger}
             {\token{nonzerodigit} \token{digit}* | "0"}
  \production{octinteger}
             {"0" \token{octdigit}+}
  \production{hexinteger}
             {"0" ("x" | "X") \token{hexdigit}+}
  \production{nonzerodigit}
             {"1"..."9"}
  \production{octdigit}
             {"0"..."7"}
  \production{hexdigit}
             {\token{digit} | "a"..."f" | "A"..."F"}
\end{productionlist}
561

562 563 564 565
Although both lower case \character{l} and upper case \character{L} are
allowed as suffix for long integers, it is strongly recommended to always
use \character{L}, since the letter \character{l} looks too much like the
digit \character{1}.
566

567 568 569 570 571 572 573 574 575 576 577 578 579 580
Plain integer decimal literals that are above the largest representable
plain integer (e.g., 2147483647 when using 32-bit arithmetic) are accepted
as if they were long integers instead.  Octal and hexadecimal literals
behave similarly, but when in the range just above the largest representable
plain integer but below the largest unsigned 32-bit number (on a machine
using 32-bit arithmetic), 4294967296, they are taken as the negative plain
integer obtained by subtracting 4294967296 from their unsigned value.  There
is no limit for long integer literals apart from what can be stored in
available memory.  For example, 0xdeadbeef is taken, on a 32-bit machine,
as the value -559038737, while 0xdeadbeeffeed is taken as the value
244837814107885L.

Some examples of plain integer literals (first row) and long integer
literals (second and third rows):
581 582 583 584

\begin{verbatim}
7     2147483647                        0177    0x80000000
3L    79228162514264337593543950336L    0377L   0x100000000L
585
      79228162514264337593543950336             0xdeadbeeffeed						    
586 587
\end{verbatim}

588

589
\subsection{Floating point literals\label{floating}}
590

591 592 593
Floating point literals are described by the following lexical
definitions:

594 595 596 597 598 599
\begin{productionlist}
  \production{floatnumber}
             {\token{pointfloat} | \token{exponentfloat}}
  \production{pointfloat}
             {[\token{intpart}] \token{fraction} | \token{intpart} "."}
  \production{exponentfloat}
600
             {(\token{intpart} | \token{pointfloat})
601 602
              \token{exponent}}
  \production{intpart}
603
             {\token{digit}+}
604 605 606 607 608
  \production{fraction}
             {"." \token{digit}+}
  \production{exponent}
             {("e" | "E") ["+" | "-"] \token{digit}+}
\end{productionlist}
609

610 611 612 613
Note that the integer and exponent parts of floating point numbers
can look like octal integers, but are interpreted using radix 10.  For
example, \samp{077e010} is legal, and denotes the same number
as \samp{77e10}.
614 615 616 617 618
The allowed range of floating point literals is
implementation-dependent.
Some examples of floating point literals:

\begin{verbatim}
619
3.14    10.    .001    1e100    3.14e-10    0e0
620 621 622
\end{verbatim}

Note that numeric literals do not include a sign; a phrase like
623 624
\code{-1} is actually an expression composed of the operator
\code{-} and the literal \code{1}.
625

626

627
\subsection{Imaginary literals\label{imaginary}}
628 629 630

Imaginary literals are described by the following lexical definitions:

631 632 633
\begin{productionlist}
  \production{imagnumber}{(\token{floatnumber} | \token{intpart}) ("j" | "J")}
\end{productionlist}
634

635
An imaginary literal yields a complex number with a real part of
636 637 638
0.0.  Complex numbers are represented as a pair of floating point
numbers and have the same restrictions on their range.  To create a
complex number with a nonzero real part, add a floating point number
Guido van Rossum's avatar
Guido van Rossum committed
639
to it, e.g., \code{(3+4j)}.  Some examples of imaginary literals:
640 641

\begin{verbatim}
Guido van Rossum's avatar
Guido van Rossum committed
642
3.14j   10.j    10j     .001j   1e100j  3.14e-10j 
643 644 645
\end{verbatim}


646
\section{Operators\label{operators}}
647 648 649 650 651

The following tokens are operators:
\index{operators}

\begin{verbatim}
652
+       -       *       **      /       //      %
653
<<      >>      &       |       ^       ~
654
<       >       <=      >=      ==      !=      <>
655 656
\end{verbatim}

657
The comparison operators \code{<>} and \code{!=} are alternate
658 659
spellings of the same operator.  \code{!=} is the preferred spelling;
\code{<>} is obsolescent.
660

661

662
\section{Delimiters\label{delimiters}}
663

664
The following tokens serve as delimiters in the grammar:
665 666 667 668
\index{delimiters}

\begin{verbatim}
(       )       [       ]       {       }
669
,       :       .       `       =       ;
670 671
+=      -=      *=      /=      //=     %=
&=      |=      ^=      >>=     <<=     **=
672 673 674
\end{verbatim}

The period can also occur in floating-point and imaginary literals.  A
675
sequence of three periods has a special meaning as an ellipsis in slices.
676 677
The second half of the list, the augmented assignment operators, serve
lexically as delimiters, but also perform an operation.
678

679
The following printing \ASCII{} characters have special meaning as part
680 681 682 683
of other tokens or are otherwise significant to the lexical analyzer:

\begin{verbatim}
'       "       #       \
684 685 686 687 688
\end{verbatim}

The following printing \ASCII{} characters are not used in Python.  Their
occurrence outside string literals and comments is an unconditional
error:
689
\index{ASCII@\ASCII}
690 691 692 693

\begin{verbatim}
@       $       ?
\end{verbatim}