[wingide-users] Disabling evaluation-on-autocomplete-highlight in the debug probe?

Russell Warren russ at perspexis.com
Fri Jan 14 09:12:25 MST 2011


On Fri, Jan 14, 2011 at 10:19 AM, Wingware Support <support at wingware.com>wrote:

> Try unchecking the Debugger / Advanced / Allow Dynamic Introspection
> preference to see if that helps.
>
> Unchecking Source Analysis / Introspect in Shells and disabling Debugger /
> Hover Over Symbols should fix it in any case but with a loss of
> functionality.
>
> We've seen problems similar to this a few times before with database code
> and one user managed to work around it by wrapping the DB class in a way
> that prevented problems.  I don't know if that's a possibility in your case.
>  An idea would be to look at the stack (w/ the traceback module in your
> code) when these calls occur and write code to have the __get__ do something
> reasonable when being called from our introspection code.  You can also look
> at os.environ which will contain WINGDB_ACTIVE when the debugger is active
> but this does not help you distinguish between your own calls and ours.
>

Thanks... I'll experiment with these.


> I'll try to look at this in more detail at some point to see if there is
> more we can do to detect these cases, or to support fixing them without
> disabling too much functionality.  If you have a small example, that might
> be useful to have.
>

Here is a small (sort of) example of it using SQLAlchemy (the only 3rd party
import needed to run it):
http://python.pastebin.com/fQcngGX8

Set a breakpoint at the line indicated and type 'joe." in the debug probe
and you'll see the emitted SQL.

Thanks,
Russ
-------------- next part --------------
An HTML attachment was scrubbed...
URL: /pipermail/wingide-users/attachments/20110114/678b116f/attachment.html


More information about the wingide-users mailing list