OK it's great that I can .printStackTrace() to see it...
But shouldn't we override JavaError.__str__ so by default an unhandled
exception originating from Java would reveal its Java trace as well?
(And presumably vice/versa).
I think on exception we should try to provide as much info as possible
to aid in debugging. Sometimes, it's a user who sees this exception,
copies it into email and sends it off to you for remote debugging.
Mike
Andi Vajda wrote:
On Fri, 13 Mar 2009, Michael McCandless wrote:
* When I hit an exception in Java, the carryover to Python fails to
include the full stack trace (sources & line numbers) from Java,
which makes debugging harder. Is that normal?
That's right and documented here [1].
Andi..
[1] http://lucene.apache.org/pylucene/jcc/documentation/readme.html#exceptions
