Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
C
cpython
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
cpython
Commits
6bab183d
Commit
6bab183d
authored
May 20, 2003
by
Fred Drake
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Markup nits.
parent
e5a55519
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
5 additions
and
5 deletions
+5
-5
Doc/tut/tut.tex
Doc/tut/tut.tex
+5
-5
No files found.
Doc/tut/tut.tex
View file @
6bab183d
...
...
@@ -208,7 +208,7 @@ or other characters that are special to the shell, it is best to quote
Note that there is a difference between
\samp
{
python file
}
and
\samp
{
python <file
}
. In the latter case, input requests from the
program, such as calls to
\
code
{
input()
}
and
\code
{
raw
_
input()
}
, are
program, such as calls to
\
function
{
input()
}
and
\function
{
raw
_
input()
}
, are
satisfied from
\emph
{
file
}
. Since this file has already been read
until the end by the parser before the program starts executing, the
program will encounter end-of-file immediately. In the former case
...
...
@@ -271,8 +271,8 @@ When an error occurs, the interpreter prints an error
message and a stack trace. In interactive mode, it then returns to
the primary prompt; when input came from a file, it exits with a
nonzero exit status after printing
the stack trace. (Exceptions handled by an
\
code
{
except
}
clause in a
\
code
{
try
}
statement are not errors in this context.) Some errors are
the stack trace. (Exceptions handled by an
\
keyword
{
except
}
clause in a
\
keyword
{
try
}
statement are not errors in this context.) Some errors are
unconditionally fatal and cause an exit with a nonzero exit; this
applies to internal inconsistencies and some cases of running out of
memory. All error messages are written to the standard error stream;
...
...
@@ -285,8 +285,8 @@ primary prompt.\footnote{
A problem with the GNU Readline package may prevent this.
}
Typing an interrupt while a command is executing raises the
\
code
{
KeyboardInterrupt
}
exception, which may be handled by a
\
code
{
try
}
statement.
\
exception
{
KeyboardInterrupt
}
exception, which may be handled by a
\
keyword
{
try
}
statement.
\subsection
{
Executable Python Scripts
\label
{
scripts
}}
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment