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
d16ddb61
Commit
d16ddb61
authored
Dec 13, 1996
by
Guido van Rossum
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Typos reported by Tamito Kajiyama.
parent
f630f6b9
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
4 additions
and
4 deletions
+4
-4
Doc/ext.tex
Doc/ext.tex
+2
-2
Doc/ext/ext.tex
Doc/ext/ext.tex
+2
-2
No files found.
Doc/ext.tex
View file @
d16ddb61
...
...
@@ -196,7 +196,7 @@ or \code{NULL} if no exception has occurred. You normally don't need
to call
\code
{
PyErr
_
Occurred()
}
to see whether an error occurred in a
function call, since you should be able to tell from the return value.
When a function
\var
{
f
}
that calls another function var
{
g
}
detects
When a function
\var
{
f
}
that calls another function
\
var
{
g
}
detects
that the latter fails,
\var
{
f
}
should itself return an error value
(e.g.
\code
{
NULL
}
or
\code
{
-1
}
). It should
\emph
{
not
}
call one of the
\code
{
PyErr
_
*()
}
functions --- one has already been called by
\var
{
g
}
.
...
...
@@ -305,7 +305,7 @@ passing it the string we just got from \code{PyArg_ParseTuple()}:
sts = system(command);
\end{verbatim}
Our
\code
{
spam.system()
}
function must return the value of
\code
{
s
y
s
}
Our
\code
{
spam.system()
}
function must return the value of
\code
{
s
t
s
}
as a Python object. This is done using the function
\code
{
Py
_
BuildValue()
}
, which is something like the inverse of
\code
{
PyArg
_
ParseTuple()
}
: it takes a format string and an arbitrary
...
...
Doc/ext/ext.tex
View file @
d16ddb61
...
...
@@ -196,7 +196,7 @@ or \code{NULL} if no exception has occurred. You normally don't need
to call
\code
{
PyErr
_
Occurred()
}
to see whether an error occurred in a
function call, since you should be able to tell from the return value.
When a function
\var
{
f
}
that calls another function var
{
g
}
detects
When a function
\var
{
f
}
that calls another function
\
var
{
g
}
detects
that the latter fails,
\var
{
f
}
should itself return an error value
(e.g.
\code
{
NULL
}
or
\code
{
-1
}
). It should
\emph
{
not
}
call one of the
\code
{
PyErr
_
*()
}
functions --- one has already been called by
\var
{
g
}
.
...
...
@@ -305,7 +305,7 @@ passing it the string we just got from \code{PyArg_ParseTuple()}:
sts = system(command);
\end{verbatim}
Our
\code
{
spam.system()
}
function must return the value of
\code
{
s
y
s
}
Our
\code
{
spam.system()
}
function must return the value of
\code
{
s
t
s
}
as a Python object. This is done using the function
\code
{
Py
_
BuildValue()
}
, which is something like the inverse of
\code
{
PyArg
_
ParseTuple()
}
: it takes a format string and an arbitrary
...
...
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