Running dev_appserver.py from the command line gives me the same "No
module named cgi" error.

The result of "defaults read ~/Library/Preferences/
com.google.GoogleAppEngineLauncher" :

=========
{
    EditDirectory = 1;
    Editor = "";
    GMClientAuthWindowSignInName = "[EMAIL PROTECTED]";
    NSNavLastCurrentDirectory = "~/Documents/workspace";
    NSNavLastRootDirectory = "~";
    NSNavPanelExpandedSizeForOpenMode = "{518, 400}";
    NSNavSidebarWidth = 120;
    "NSTableView Columns NSNavOutlineColumnSettings.v1" =     (
        <040b7374 7265616d 74797065 6481e803 84014084 8484084e
53537472 696e6701 8484084e 534f626a 65637400 8584012b 1c4e534e
61764469 73706c61 794e616d 6546696c 6550726f 70657274 7986>,
        225,
        <040b7374 7265616d 74797065 6481e803 84014084 8484084e
53537472 696e6701 8484084e 534f626a 65637400 8584012b 184e534e
61764d6f 64446174 6546696c 6550726f 70657274 7986>,
        145
    );
    "NSTableView Hidden Columns NSNavOutlineColumnSettings.v1" =     (
    );
    "NSTableView Sort Ordering NSNavOutlineColumnSettings.v1" =     (
        <040b7374 7265616d 74797065 6481e803 84014084 8484084e
53537472 696e6701 8484084e 534f626a 65637400 8584012b 184e534e
61764d6f 64446174 6546696c 6550726f 70657274 7986>,
        0
    );
    "NSToolbar Configuration DocTB" =     {
        "TB Display Mode" = 1;
        "TB Icon Size Mode" = 1;
        "TB Is Shown" = 1;
        "TB Item Identifiers" =         (
            Run,
            Stop,
            Browse,
            Logs,
            "SDK Console",
            NSToolbarSeparatorItem,
            Edit,
            NSToolbarFlexibleSpaceItem,
            Deploy,
            Dashboard
        );
        "TB Size Mode" = 1;
        "TB Visibility Priority Values" =         {
        };
    };
}
=========

"os.path.exists(os.path.join(os.path.dirname(os.__file__), 'cgi.py'))"
gives me a value of True.

greg


On Oct 8, 9:06 pm, "Marzia Niccolai" <[EMAIL PROTECTED]> wrote:
> Yet more troubleshooting requests :)
>
> This may be more specific than just 1.1.5 + 10.5.5 as we have cases where
> this installation is working.
>
> If you could send the results of running this command on the command line:
> defaults read ~/Library/Preferences/com.google.GoogleAppEngineLauncher
>
> Also, the entire output in the Console window, such as:
> *** Running dev_appserver with the following flags:
>    --admin_console_server= --port=8080 --datastore_path=/Users/name/qqqqq
> --debug
> Python command: /usr/bin/python
>
> And finally when you run python from the shell, what is the output of:
> import os
> os.path.exists(os.path.join(os.path.dirname(os.__file__), 'cgi.py'))
>
> Thanks,
> Marzia
>
> On Wed, Oct 8, 2008 at 11:30 AM, Marzia Niccolai <[EMAIL PROTECTED]> wrote:
> > Hi,
>
> > Another question for those experiencing the issue - what is the output when
> > you type 'python' in to your command line in the Mac shell?
>
> > Thanks,
> > Marzia
>
> > On Wed, Oct 8, 2008 at 11:19 AM, Marzia Niccolai <[EMAIL PROTECTED]> wrote:
>
> >> Hi,
>
> >> I couldn't find this filed so I went ahead:
> >>http://code.google.com/p/googleappengine/issues/detail?id=778
>
> >> The scope so far seems to be limited to 10.5.5, and we'll keep you updated
> >> on the progress.  I wonder if you can still run the SDK by making the
> >> symlinks and running from the command line?
>
> >> Thanks for the troubleshooting help.
>
> >> -Marzia
>
> >> On Wed, Oct 8, 2008 at 10:39 AM, Greg <[EMAIL PROTECTED]> wrote:
>
> >>> I'm having the same error (on OS 10.5.5 and Launcher 1.1.5). I tried
> >>> explicit setting my Python path. It didn't fix the problem
>
> >>> Greg
>
> >>> On Oct 8, 5:59 pm, "Marzia Niccolai" <[EMAIL PROTECTED]> wrote:
> >>> > Hi,
>
> >>> > Thanks.  Right now it seems that this is an issue specific to 10.5.5 +
> >>> the
> >>> > App Engine Launcher.  Since I don't have access to a 10.5.5
> >>> installation of
> >>> > Mac OS, I'd like to ask you to try one more step.
>
> >>> > Would it be possible for you to explicitly set the Python Path in the
> >>> > Launcher to your python installation?  Or if someone else has 10.5.5 +
> >>> the
> >>> > 1.1.5 SDK if you could do this and see if it solves the issue that
> >>> would be
> >>> > appreciated.
>
> >>> > Thanks,
> >>> > Marzia
>
> >>> > On Wed, Oct 8, 2008 at 8:24 AM, Gijsbert <[EMAIL PROTECTED]>
> >>> wrote:
>
> >>> > > Didn't read the question correctly.
> >>> > > Python Path in the launcher is empty. But logging sys.path still
> >>> > > reported the correct paths (a whole bunch of app engine paths, then
> >>> > > the normal python2.5 paths).
>
> >>> > > On Oct 6, 12:59 pm, "Marzia Niccolai" <[EMAIL PROTECTED]> wrote:
> >>> > > > Hi,
>
> >>> > > > What is the Python Path that you have in your launcher?
>
> >>> > > > Thanks,
> >>> > > > Marzia
>
> >>> > > > On Sun, Oct 5, 2008 at 2:17 PM, Gijsbert <
> >>> [EMAIL PROTECTED]>
> >>> > > wrote:
>
> >>> > > > > Hi,
>
> >>> > > > > Since upgrading to GAE 1.1.5 my app stopped working,
> >>> dev_appserver.py
> >>> > > > > can't import cgi, urllib, traceback, etc:
>
> >>> > > > > <type 'exceptions.ImportError'>: No module named cgi
> >>> > > > >      args = ('No module named cgi',)
> >>> > > > >      message = 'No module named cgi
>
> >>> > > > > Importing these from python2.5 shell works fine.
>
> >>> > > > > It might be a MacOS (10.5.5) issue, I just ran the same app on my
> >>> > > > > linux box and it works there (well, I could not import
> >>> > > > > wsgiref.handlers any more, but changing to run_wsgi_app() made
> >>> that
> >>> > > > > import unnecessary).
>
> >>> > > > > A fix would be awesome, since my linux box is old and cranky.
>
> >>> > > > > Best regards,
> >>> > > > > Gijsbert
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google App Engine" 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/google-appengine?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to