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
48b5b1a8
Commit
48b5b1a8
authored
Feb 26, 1999
by
Fred Drake
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
extract_tb(): Only describe this function once. Problem reported by
Jonathan Giddy <jon@dgs.monash.edu.au>.
parent
cb52351f
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
12 additions
and
23 deletions
+12
-23
Doc/lib/libtraceback.tex
Doc/lib/libtraceback.tex
+12
-23
No files found.
Doc/lib/libtraceback.tex
View file @
48b5b1a8
...
...
@@ -28,20 +28,8 @@ If \var{file} is omitted or \code{None}, the output goes to
object to receive the output.
\end{funcdesc}
\begin{funcdesc}
{
extract
_
tb
}{
traceback
\optional
{
, limit
}}
Return a list of up to
\var
{
limit
}
``pre-processed'' stack trace
entries extracted from
\var
{
traceback
}
. It is useful for alternate
formatting of stack traces. If
\var
{
limit
}
is omitted or
\code
{
None
}
,
all entries are extracted. A ``pre-processed'' stack trace entry is a
quadruple (
\var
{
filename
}
,
\var
{
line number
}
,
\var
{
function name
}
,
\var
{
line text
}
) representing the information that is usually printed
for a stack trace. The
\var
{
line text
}
is a string with leading and
trailing whitespace stripped; if the source is not available it is
\code
{
None
}
.
\end{funcdesc}
\begin{funcdesc}
{
print
_
exception
}{
type, value,
traceback
\optional
{
, limit
\optional
{
, file
}}}
\begin{funcdesc}
{
print
_
exception
}{
type, value, traceback
\optional
{
,
limit
\optional
{
, file
}}}
Print exception information and up to
\var
{
limit
}
stack trace entries
from
\var
{
traceback
}
to
\var
{
file
}
.
This differs from
\function
{
print
_
tb()
}
in the
...
...
@@ -73,15 +61,16 @@ frame to start. The optional \var{limit} and \var{file} arguments have the
same meaning as for
\function
{
print
_
exception()
}
.
\end{funcdesc}
\begin{funcdesc}
{
extract
_
tb
}{
tb
\optional
{
, limit
}}
Return a list containing the raw (unformatted) traceback information
extracted from the traceback object
\var
{
tb
}
. The optional
\var
{
limit
}
argument has the same meaning as for
\function
{
print
_
exception()
}
. The items in the returned list are
4-tuples containing the following values: filename, line number,
function name, and source text line. The source text line is stripped
of leading and trailing whitespace; it is
\code
{
None
}
when the source
text file is unavailable.
\begin{funcdesc}
{
extract
_
tb
}{
traceback
\optional
{
, limit
}}
Return a list of up to
\var
{
limit
}
``pre-processed'' stack trace
entries extracted from the traceback object
\var
{
traceback
}
. It is
useful for alternate formatting of stack traces. If
\var
{
limit
}
is
omitted or
\code
{
None
}
, all entries are extracted. A
``pre-processed'' stack trace entry is a quadruple (
\var
{
filename
}
,
\var
{
line number
}
,
\var
{
function name
}
,
\var
{
text
}
) representing
the information that is usually printed for a stack trace. The
\var
{
text
}
is a string with leading and trailing whitespace
stripped; if the source is not available it is
\code
{
None
}
.
\end{funcdesc}
\begin{funcdesc}
{
extract
_
stack
}{
\optional
{
f
\optional
{
, limit
}}}
...
...
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