Feedback on experimental Mac Launcher for Python

53 views
Skip to first unread message

Brian Quinlan

unread,
May 17, 2012, 12:59:19 AM5/17/12
to google-a...@googlegroups.com
Hi,

Along with the usual components of the App Engine 1.6.5 release, we
also released an experimental version of the Mac OS X Launcher that
includes a siloed version of Python 2.7 (see
https://developers.google.com/appengine/downloads). Our reason for
providing this was to reduce the number of dependencies that Mac users
needed to download before they have a usable SDK.

This experimental launcher was downloaded >500 times but we haven't
received any feedback about it. Could anyone who downloaded and try it
please respond to this thread saying whether they had any problems or
not?

The more feedback we get, the better our release will be and your help
is really appreciated!

Cheers,
Brian

alex

unread,
May 17, 2012, 2:54:39 AM5/17/12
to google-a...@googlegroups.com
Hey Brian,

I did try the Mac OS version a couple times. The idea is nice. Not only because of "to reduce the number of deps". I think it's good to have dev appserver running in a "clean", separate environment, closer to how it works in production (e.g. I sometimes mess up my python 2.7 and site packages, making them do weird stuff, experimenting).

The reason I'm not using it daily (both with and w/o bundled python) is that I'd have it frozen (the Launcher app) so I had to "forse quit" it from Activity Monitor. And it happens too often so, at the end of the day I find myself using SDK *.py scripts directly from the Terminal (which I don't mind actually).

Unfortunately, I can't really provide some deterministic steps to reproduce "freezing" right now. But, I noticed it almost always happend when I click "stop" (to stop the dev appserver).


-- alex

Brian Quinlan

unread,
May 17, 2012, 8:15:54 AM5/17/12
to google-a...@googlegroups.com
Hi Alex,

Thanks very much for the feedback!

On Thu, May 17, 2012 at 4:54 PM, alex <al...@cloudware.it> wrote:
> Hey Brian,
>
> I did try the Mac OS version a couple times. The idea is nice. Not only
> because of "to reduce the number of deps". I think it's good to have dev
> appserver running in a "clean", separate environment, closer to how it works
> in production (e.g. I sometimes mess up my python 2.7 and site packages,
> making them do weird stuff, experimenting).
>
> The reason I'm not using it daily (both with and w/o bundled python) is that
> I'd have it frozen (the Launcher app) so I had to "forse quit" it from
> Activity Monitor. And it happens too often so, at the end of the day I find
> myself using SDK *.py scripts directly from the Terminal (which I don't mind
> actually).
>
> Unfortunately, I can't really provide some deterministic steps to reproduce
> "freezing" right now. But, I noticed it almost always happend when I click
> "stop" (to stop the dev appserver).

Did this problem occur with the regular launcher or just the experimental one?

Cheers,
Brian

>
> -- alex
>
>
> On Thursday, May 17, 2012 6:59:19 AM UTC+2, Brian Quinlan wrote:
>>
>> Hi,
>>
>> Along with the usual components of the App Engine 1.6.5 release, we
>> also released an experimental version of the Mac OS X Launcher that
>> includes a siloed version of Python 2.7 (see
>> https://developers.google.com/appengine/downloads). Our reason for
>> providing this was to reduce the number of dependencies that Mac users
>> needed to download before they have a usable SDK.
>>
>> This experimental launcher was downloaded >500 times but we haven't
>> received any feedback about it. Could anyone who downloaded and try it
>> please respond to this thread saying whether they had any problems or
>> not?
>>
>> The more feedback we get, the better our release will be and your help
>> is really appreciated!
>>
>> Cheers,
>> Brian
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-appengine/-/bG6kFyDQ_cIJ.
> To post to this group, send email to google-a...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengi...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.

alex

unread,
May 17, 2012, 9:38:31 AM5/17/12
to google-a...@googlegroups.com
It occurs on both, the regular and experimental launchers. In fact, I don't believe it is something related to the differences between the two.

Actually, I've just launched it again with a minimal app, a single page rendered by Jinja2 on webapp2. 

It got frozen when I tried to stop the app server during an ongoing request handling. In fact, in the attached screenshot you'll see "KeyboardInterrupt" standard exception that normally happens if you CTRL-C the process in a terminal during a request handling, only that Launcher now got stuck and not even responding to "quit" so I've just had to force it.

I even checked out the (regular) launcher source code once to see if I could find out what's going on but I didn't really have time to get my hands on it.

Hope that helps!

PS I'm running Lion, but it happend to me before on Snow Leo too.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
Screen Shot 2012-05-17 at 3.25.13 PM.png

alex

unread,
May 17, 2012, 10:31:09 AM5/17/12
to google-a...@googlegroups.com
Brian, if it helps: 

create a new app and put "time.sleep(5)" as the first line of a "def get(self)" in a request handler. Now, run the app, click on Browse and, while browser's waiting those 5 sec, switch back to the Launcher and click "Stop". You should be able to get that freezing behavior. Well, unless there's something weird with my local setup. In the latter case I'd love to be able to figure out what it is as I really like the launcher and its simplicity.
Reply all
Reply to author
Forward
0 new messages