From: SourceForge.net <no...@so...> - 2006-06-02 16:01:00
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3761084 By: fabioz Well, Pydev uses the tracing facility for doing the debugger (as all other debuggers), so, maybe when you make that import in turbogears it changes that tracing facility (sys.settrace and threading.settrace). It might be worth asking the turbogears authors if turbogears changes that for some reason... if they do, it has to be changed there, as the debugger will be 'out of the loop' for checking breakpoints (and there's nothing pydev can do about it). If that's not the case, then it might be a bug, but I think that this is more unlikely, as just making that import breaks it. Cheers, Fabio ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=293649 |