Terribly sorry to mention this, but you reminded me of this classic old joke:
Patient: "Doctor, it hurts when I do this...." (poking himself in the eyeball) Doctor: "Then don't do that." In your case, I'll recommend that you don't do that, and instead, do this: 1)start menu 2)cmd 3)C:\Program Files\Google\google_appengine\appcfg.py update path-to-- your-app.yaml The Google App Engine people tried to trick you into poking yourself in the eye, by making two different modules, each named appcfg.py. And they didn't make it clear in their documentation which file you should use. So don't feel too bad. and, while I'm giving you recommendations: 2) Download the latest version of the SDK; it will probably save you from hurting yourself a few more times. On Mar 1, 2:07 am, andrewliu <mrliulip...@gmail.com> wrote: > the environment: > 1) GoogleAppEngine_1.1.0.msi (1.1.0 - 5/28/08) > 2)Python2.5.4(Dec 23.2008) > > the step is > 1)start menu > 2)cmd > 3)C:\Program Files\Google>google_appengine\google\appengine\tools > \appcfg.py update > 1 > Traceback (most recent call last): > File "C:\Program Files\Google\google_appengine\google\appengine\tools > \appcfg.p > y", line 48, in <module> > import google > ImportError: No module named google > > Can you help me? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
