Thanks for your help. I tried your suggestions (except for the new
command, which I couldn't find), but it isn't fixed yet. I could
probably benefit from a better understanding on what it is that the
sequence of commands given in the cookbook is trying to do. I don't
really understand whether or how dev_appserver makes use of modules
installed, either in the system or in the virtualenv, and I don't
understand how appengine-monkey works.
Also, I know that SDK 1.1.2 works for me, and not SDK 1.1.3 or
greater, but I know that you have installed on an older SDK and then
upgraded the SDK and it works. But I tried that, and it didn't work
for me. Is it possible that I actually did exactly the same thing that
you did to install, but that it didn't work for me because I am on a
different platform? I am using Debian GNU/Linux x86_64. Is it known if
anyone has successfully gotten SDK >1.1.3 to run on Debian using the
cookbook instructions?
I suspect that the modules installed in the virtualenv are not being
used by the appserver, which is why I get errors suggesting that it is
looking in /usr/lib.
I don't really understand why the virtualenv modules WOULD be used in
the first place, since I deactivate the virtualenv before running
dev_appserver.py. Is dev_appserver.py supposed to be using the modules
in the virtualenv? If so, how do I confirm that it is doing so? If
not, then why would "import site" fail when run on the appserver,
because I can run "python -m site" from the commandline with no
problems?
More details below.
> Sometimes reinstalling the
> application ("python setup.py develop") fixes ImportError's.
Tried it but it didn't work.
> You should not be using nonstandard libraries installed in /usr/lib,
> because they will not be available in the server environment.
> You'll
> have to install Setuptools into the virtualenv.
Is the appserver supposed to be using libraries from /usr/lib at all?
I was under the impression that the sequence of commands I described
(in my script) was supposed to create a virtualenv that would be
populated with all the needed libraries, and that the appserver would
use those.
As for setuptools, it seems that it already is installed in my
virtualenv; there is a directory at
testsite/lib/python2.5/site-packages/setuptools-0.6c9-py2.5.egg/
> Appengine-monkey has a new command to create the virtualenv,
> which I
> haven't tried yet so it's not in the wiki instructions, but Ian
> recommends it. I'd try starting over with that and seeing if it
> helps.
could you tell me where to look for further information about the new
command? here is where i have tried to look so far:
* the "docs" directory in SVN is empty except for a license file
* http://code.google.com/p/appengine-monkey/ just says to take a look
at http://code.google.com/p/appengine-monkey/wiki/Pylons , which looks
like another version of the cookbook page
* running python appengine-monkey/appengine-boot.py --help
> And use the --no-site-packages option, whatever it's called.
Tried it but it didn't work.
thanks,
bayle
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---
