mirror of
				https://github.com/python/cpython.git
				synced 2025-10-30 09:57:32 +00:00 
			
		
		
		
	extract_tb(): Only describe this function once. Problem reported by
Jonathan Giddy <jon@dgs.monash.edu.au>.
This commit is contained in:
		
							parent
							
								
									390636382a
								
							
						
					
					
						commit
						43b34da656
					
				
					 1 changed files with 12 additions and 23 deletions
				
			
		|  | @ -28,20 +28,8 @@ If \var{file} is omitted or \code{None}, the output goes to | ||||||
| object to receive the output. | object to receive the output. | ||||||
| \end{funcdesc} | \end{funcdesc} | ||||||
| 
 | 
 | ||||||
| \begin{funcdesc}{extract_tb}{traceback\optional{, limit}} | \begin{funcdesc}{print_exception}{type, value, traceback\optional{, | ||||||
| Return a list of up to \var{limit} ``pre-processed'' stack trace |                                   limit\optional{, file}}} | ||||||
| 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}}} |  | ||||||
| Print exception information and up to \var{limit} stack trace entries | Print exception information and up to \var{limit} stack trace entries | ||||||
| from \var{traceback} to \var{file}. | from \var{traceback} to \var{file}. | ||||||
| This differs from \function{print_tb()} in the | 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()}. | same meaning as for \function{print_exception()}. | ||||||
| \end{funcdesc} | \end{funcdesc} | ||||||
| 
 | 
 | ||||||
| \begin{funcdesc}{extract_tb}{tb\optional{, limit}} | \begin{funcdesc}{extract_tb}{traceback\optional{, limit}} | ||||||
| Return a list containing the raw (unformatted) traceback information | Return a list of up to \var{limit} ``pre-processed'' stack trace | ||||||
| extracted from the traceback object \var{tb}.  The optional | entries extracted from the traceback object \var{traceback}.  It is | ||||||
| \var{limit} argument has the same meaning as for | useful for alternate formatting of stack traces.  If \var{limit} is | ||||||
| \function{print_exception()}.  The items in the returned list are | omitted or \code{None}, all entries are extracted.  A | ||||||
| 4-tuples containing the following values: filename, line number, | ``pre-processed'' stack trace entry is a quadruple (\var{filename}, | ||||||
| function name, and source text line.  The source text line is stripped  | \var{line number}, \var{function name}, \var{text}) representing | ||||||
| of leading and trailing whitespace; it is \code{None} when the source | the information that is usually printed for a stack trace.  The | ||||||
| text file is unavailable. | \var{text} is a string with leading and trailing whitespace | ||||||
|  | stripped; if the source is not available it is \code{None}. | ||||||
| \end{funcdesc} | \end{funcdesc} | ||||||
| 
 | 
 | ||||||
| \begin{funcdesc}{extract_stack}{\optional{f\optional{, limit}}} | \begin{funcdesc}{extract_stack}{\optional{f\optional{, limit}}} | ||||||
|  |  | ||||||
		Loading…
	
	Add table
		Add a link
		
	
		Reference in a new issue
	
	 Fred Drake
						Fred Drake