Traceback does not include module path

When a traceback is generated, it only shows the module name, without giving the path to that module.

Given two script modules, app.foo.shared and app.bar.shared, an error in one will cause a trace like this:

Traceback (most recent call last):
  File "<event:actionPerformed>", line 1, in <module>
  File "<module:shared>", line 103, in func

There is no way of knowing whether the error was caused in app.foo.shared.func or app.bar.shared.func without tracing the code by hand.

A normal python traceback looks something like this:

Traceback (most recent call last):
  File "pythontests/exception.py", line 9, in <module>

It would be great if this could be fixed.

Thanks.

Better?


Excellent, thanks very much.