At first thanks for your answers!!! On 16 Mrz., 21:16, Carl Banks <pavlovevide...@gmail.com> wrote: > Here you raise an exception with a C statement, > and catch and print it in the very next line. The exception doesn't > exit from Python code so there are no lines to print.
Exactly, I dont expect any line/file information. I am just looking forward for a solution how to solve that. I would like to avoid the use of the debugger in this case. My ideas: 1. I thought the return value might contain any information where it is from. 2. Otherwise it would be cool if there are any information available in which line, file the last called function/method exited. Bye, moerchendiser2k3 -- http://mail.python.org/mailman/listinfo/python-list
