[wingide-users] GAE and the Debug Probe

[Mark Jones]

It appears that imp is not available on GAE at all, so they patch it away because django actually calls find_module.  I'm trying now to figure out how to detect real GAE vs Dev GAE so I can NOT patch it out on the dev platform.

--- On Wed, 7/22/09, Wingware Support <support at wingware.com> wrote:

> From: Wingware Support <support at wingware.com>
> Subject: Re: [wingide-users] GAE and the Debug Probe
> To: mdjones0978-wingide at yahoo.com
> Cc: "Wing IDE Users list" <wingide-users at wingware.com>
> Date: Wednesday, July 22, 2009, 10:24 AM
> Mark Jones wrote:
> > I'm using GAE with Django helper.  The Debug
> probe has become useless (noticed it before I added the
> Django helper to the project)
> > 
> >>>> groups
> > Traceback (most recent call last):
> >   File "<string>", line 1, in
> <string>
> > RuntimeError: lost __builtin__
> > 
> > I'm suspecting this to be culprit (it appears to be
> what cause wingdbstub.py to fail as well:
> > 
> > def find_module(name, path=None):
> >   """Django needs imp.find_module, but
> it works fine if nothing is found."""
> >   raise ImportError
> > 
> > Any ideas on what to do to fix it?
> 
> Yes, if they are replacing imp.find_module with the above
> that would be a bit
> of a problem for any code that uses that.... and we do use
> it to find our
> debugger modules.
> 
> The only thing I can recommend is not monkey patching imp,
> assuming that
> is what is being done here.  I don't quite understand
> why they would do
> this.
> 
> -- 
> Stephan Deibel
> Wingware | Python IDE
> Advancing Software Development
> 
> www.wingware.com
> 
>