traceback

问题 I want to extract error detail from traceback, those tracebacks are extract from log file by using this method, and there are many different kinds of tracebacks, like below: Traceback (most recent call last): File "/usr/lib/python2.7/runpy.py", line 174, in _run_module_as_main "__main__", fname, loader, pkg_name) File "/usr/lib/python2.7/runpy.py", line 72, in _run_code exec code in run_globals File "/root/env/common/test/test/__main__.py", line 5, in <module> main() File "/root/env/common

问题 I am getting this error when I am simply trying to run play command from command prompt in windows. C:\Users\naveenreddy>play Traceback (most recent call last): File "E:\andrew\structure\play-1.2\play", line 13, in <module> from play.application import PlayApplication File "E:\andrew\structure\play-1.2\framework\pym\play\application.py", line 5, in <module> import socket File "C:\Python27\lib\socket.py", line 47, in <module> import _socket ImportError: DLL load failed: %1 is not a valid Win32

问题 I have been using emacs snapshot for a while now but recently it has been crashing a lot. So I switched to Emacs 24. But once I installed it and started it up it started showing error and wouldn't load anything in my init.el when I ran it in debug mode, I got this. Debugger entered--Lisp error: (void-function package--description-file) (package--description-file pkg-dir) (expand-file-name (package--description-file pkg-dir) pkg-dir) The full trace is here. Any help in fixing this or

问题 I have been using emacs snapshot for a while now but recently it has been crashing a lot. So I switched to Emacs 24. But once I installed it and started it up it started showing error and wouldn't load anything in my init.el when I ran it in debug mode, I got this. Debugger entered--Lisp error: (void-function package--description-file) (package--description-file pkg-dir) (expand-file-name (package--description-file pkg-dir) pkg-dir) The full trace is here. Any help in fixing this or

问题 Following is sample code, aim is just to merges text files from give folder and it's sub folder. i am getting Traceback occasionally so not sure where to look. also need some help to enhance the code to prevent blank line being merge & to display no lines in merged/master file. Probably it's good idea to before merging file, some cleanup should performed or just to ignores blank line during merging process. Text file in folder is not more then 1000 lines but aggregate master file could cross

问题 According to How to exit from Python without traceback? , calling sys.exit() in a Python script should exit silently without a traceback. import sys sys.exit(0) However, when I launch my script from the command line on Windows 7 with python -i "exit.py" , (or from Notepad++), a traceback for a SystemExit exception is displayed. U:\>python -i "exit.py" Traceback (most recent call last): File "exit.py", line 2, in <module> sys.exit(0) SystemExit: 0 >>> Why is sys.exit() displaying a traceback

问题 I have a matrix like this: http://i.imgur.com/3HiEBm4.png You can load it like this: matrix = structure(c("-", "-", "C", "G", "C", "A", "-", "0", "V", "V", "V", "V", "C", "H", "D", "V", "DV", "V", "A", "H", "H", "D", "DV", "D", "C", "H", "DH", "DH", "D", "V", "G", "H", "H", "D", "H", "D", "T", "H", "H", "H", "DH", "DH", "A", "H", "H", "H", "DH", "D", "T", "H", "H", "H", "DH", "H"), .Dim = c(6L, 9L)) Starting at the bottom-right corner, the goal is to follow the directions (D = move diagonally

问题 I have IronPython hosted within my application, whenever I catch an exception thrown from a script, I get unhelpful gibberish like this: IronPython.NewTypes.System.Exception_1$1: Error occurred during conversion ---> Microsoft.Scripting.ArgumentTypeException: expected int, got DispMethod at _stub_$245##245(Closure , CallSite , Object ) at Microsoft.Scripting.Actions.MatchCaller.Call1[T0,TRet](Func`3 target, CallSite site, Object[] args) at Microsoft.Scripting.Actions.CallSite`1

问题 In python you can compile() string to be executed faster with exec(). But as soon as i use it, we lost information when an exception happen in the exec. For example, here is a code snippet that calling a unknown method (for demo purposes): code = 'my_unknown_method()' bytecode = compile(code, '<string>', 'exec') And later, i'm calling exec on that bytecode: exec bytecode The traceback showed is: Traceback (most recent call last): File "test.py", line 3, in <module> exec bytecode File "<string

问题 Is there a simple way to disable the logging of an exception stack trace in Python 3, either in a Handler or Formatter ? I need the stack trace in another Handler , so setting exc_info=False , in the call to the Logger is not an option. Is there a simpler way than just defining my own Formatter ? 回答1: The easiest option to disable per handler traceback output is to add a custom logging.Filter subclass that alters the record object (rather than filter out records). The filter simply has to set