sikuli-driver team mailing list archive

[shawn kirsch <shawn.kirsch@xxxxxxxxxxxxxxxx>]

Public bug reported:

If I have a lib called testLib and I import it into another moduel say
curModule and then call a function in testLib, if it fails in the
function I'm calling to testLib it will say there was an error in
curModule on line whatever, although it's actually failing on a separate
line in the testLib.  Can sikuli not inspect it deep enough?  this make
debugging a pain in the ass.

** Affects: sikuli
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/1230928

Title:
  Error Tracebacks Display Wrong Line

Status in Sikuli:
  New

Bug description:
  If I have a lib called testLib and I import it into another moduel say
  curModule and then call a function in testLib, if it fails in the
  function I'm calling to testLib it will say there was an error in
  curModule on line whatever, although it's actually failing on a
  separate line in the testLib.  Can sikuli not inspect it deep enough?
  this make debugging a pain in the ass.

To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/1230928/+subscriptions