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
b88986f2
Commit
b88986f2
authored
Jun 10, 1996
by
Guido van Rossum
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Note that EOF is ^Z on DOS. Spell Unix as \UNIX in some more places.
Note that .pyc files are platform independent.
parent
b7e3b547
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
14 additions
and
8 deletions
+14
-8
Doc/tut.tex
Doc/tut.tex
+7
-4
Doc/tut/tut.tex
Doc/tut/tut.tex
+7
-4
No files found.
Doc/tut.tex
View file @
b88986f2
...
...
@@ -205,7 +205,8 @@ When commands are read from a tty, the interpreter is said to be in
with the
{
\em
primary
\
prompt
}
, usually three greater-than signs (
{
\tt
>>>
}
); for continuation lines it prompts with the
{
\em
secondary
\
prompt
}
,
by default three dots (
{
\tt
...
}
). Typing an EOF (Control-D)
by default three dots (
{
\tt
...
}
). Typing an EOF character
(Control-D on
{
\UNIX
}
, Control-Z on DOS or Windows)
at the primary prompt causes the interpreter to exit with a zero exit
status.
...
...
@@ -275,7 +276,9 @@ Whenever {\tt spam.py} is successfully compiled, an attempt is made to
write the compiled version to
{
\tt
spam.pyc
}
. It is not an error if
this attempt fails; if for any reason the file is not written
completely, the resulting
{
\tt
spam.pyc
}
file will be recognized as
invalid and thus ignored later.
invalid and thus ignored later. The contents of the
{
\tt
spam.pyc
}
file is platform independent, so a Python module directory can be
shared by machines of different architectures.
\subsection
{
Executable Python scripts
}
...
...
@@ -3205,9 +3208,9 @@ exactly as if \code{cmp(x, y)} were a binary operator like \code{+}
\section
{
Unix Signal Handling
}
On
Unix
, Python now supports signal handling. The module
On
{
\UNIX
}
, Python now supports signal handling. The module
\code
{
signal
}
exports functions
\code
{
signal
}
,
\code
{
pause
}
and
\code
{
alarm
}
, which act similar to their
Unix
counterparts. The
\code
{
alarm
}
, which act similar to their
{
\UNIX
}
counterparts. The
module also exports the conventional names for the various signal
classes (also usable with
\code
{
os.kill()
}
) and
\code
{
SIG
_
IGN
}
and
\code
{
SIG
_
DFL
}
. See the section on
\code
{
signal
}
in the Library
...
...
Doc/tut/tut.tex
View file @
b88986f2
...
...
@@ -205,7 +205,8 @@ When commands are read from a tty, the interpreter is said to be in
with the
{
\em
primary
\
prompt
}
, usually three greater-than signs (
{
\tt
>>>
}
); for continuation lines it prompts with the
{
\em
secondary
\
prompt
}
,
by default three dots (
{
\tt
...
}
). Typing an EOF (Control-D)
by default three dots (
{
\tt
...
}
). Typing an EOF character
(Control-D on
{
\UNIX
}
, Control-Z on DOS or Windows)
at the primary prompt causes the interpreter to exit with a zero exit
status.
...
...
@@ -275,7 +276,9 @@ Whenever {\tt spam.py} is successfully compiled, an attempt is made to
write the compiled version to
{
\tt
spam.pyc
}
. It is not an error if
this attempt fails; if for any reason the file is not written
completely, the resulting
{
\tt
spam.pyc
}
file will be recognized as
invalid and thus ignored later.
invalid and thus ignored later. The contents of the
{
\tt
spam.pyc
}
file is platform independent, so a Python module directory can be
shared by machines of different architectures.
\subsection
{
Executable Python scripts
}
...
...
@@ -3205,9 +3208,9 @@ exactly as if \code{cmp(x, y)} were a binary operator like \code{+}
\section
{
Unix Signal Handling
}
On
Unix
, Python now supports signal handling. The module
On
{
\UNIX
}
, Python now supports signal handling. The module
\code
{
signal
}
exports functions
\code
{
signal
}
,
\code
{
pause
}
and
\code
{
alarm
}
, which act similar to their
Unix
counterparts. The
\code
{
alarm
}
, which act similar to their
{
\UNIX
}
counterparts. The
module also exports the conventional names for the various signal
classes (also usable with
\code
{
os.kill()
}
) and
\code
{
SIG
_
IGN
}
and
\code
{
SIG
_
DFL
}
. See the section on
\code
{
signal
}
in the Library
...
...
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