ImportError: No module named inspect

[Matthew]

This is a duplicate of Issue 77 http://code.google.com/p/tipfy/issues/detail?id=77,
but I think it bears repeating because I've done extensive testing and
cannot get my head around it.

When I fire up the "Hello World" example from Tipfy 0.6.3 or 0.6.4,
instead of seeing the proper output, I get the error "ImportError: No
module named inspect". The inspect module is called by werkzeug right
away. I've tested with each combination of the following and get the
same result: these 2 Tipfy versions, the ready-built archives and the
do-it-yourself archives, and AppEngine SDKs 1.3.8-1.4.2. I've also
checked that I can call "import inspect" from the Python command line
with no trouble.

What's really troubling is that I'm running another 0.6.3 application
on the SAME MACHINE with NO TROUBLE. I've even upgraded its libraries
along the way. Why would my version of 0.6.3 run fine, but not a newly-
downloaded version?

Any insight is greatly appreciated. I've posted an abridged stack
trace below.

Thanks!
Matthew

Traceback (most recent call last):
File "/home/matthew/dev/sdks/google_appengine_1.4.2/google/appengine/
tools/dev_appserver.py", line 3245, in _HandleRequest
self._Dispatch(dispatcher, self.rfile, outfile, env_dict)
File "/home/matthew/dev/sdks/google_appengine_1.4.2/google/appengine/
tools/dev_appserver.py", line 3186, in _Dispatch
base_env_dict=env_dict)
. . .
File "/home/matthew/dev/sdks/google_appengine_1.4.2/google/appengine/
tools/dev_appserver.py", line 1798, in LoadModuleRestricted
description)
File "distlib/werkzeug/_internal.py", line 11, in <module>
ImportError: No module named inspect

[Yonsy Solis]

Matthew wrote:
> This is a duplicate of Issue 77 http://code.google.com/p/tipfy/issues/detail?id=77,
> but I think it bears repeating because I've done extensive testing and
> cannot get my head around it.
>
> When I fire up the "Hello World" example from Tipfy 0.6.3 or 0.6.4,
> instead of seeing the proper output, I get the error "ImportError: No
> module named inspect". The inspect module is called by werkzeug right
> away. I've tested with each combination of the following and get the
> same result: these 2 Tipfy versions, the ready-built archives and the
> do-it-yourself archives, and AppEngine SDKs 1.3.8-1.4.2. I've also
> checked that I can call "import inspect" from the Python command line
> with no trouble.
>
> What's really troubling is that I'm running another 0.6.3 application
> on the SAME MACHINE with NO TROUBLE. I've even upgraded its libraries
> along the way. Why would my version of 0.6.3 run fine, but not a newly-
> downloaded version?
>
> Any insight is greatly appreciated. I've posted an abridged stack
> trace below.

are u using virtualenv in your test version and/or your deployed app?

i suspect that virtualenv is related in this problem, btw i dont use
virtualenv since buildout 1.5.x give a really isolated environment
now.

--
Yonsy Solis

[Matthew]

I am using virtualenv. What's strange is that I also get the same
error if I deactivate the environment and run the script.

On Mar 10, 8:59 am, Yonsy Solis <yonsy.so...@gmail.com> wrote:
> Matthew wrote:

> > This is a duplicate of Issue 77http://code.google.com/p/tipfy/issues/detail?id=77,