aminnelson / google-appengine-mac-launcher

Automatically exported from code.google.com/p/google-appengine-mac-launcher
Apache License 2.0
0 stars 0 forks source link

Python path has no apparent effect #1

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Have an existing ~/Library/Application
Support/GoogleAppengineLauncher/Projects.plist from a previous revision of
the GoogleAppengineLauncher
2. Attempt to change the Python path in the laucher (e.g to
/opt/local/bin/python2.5)

What is the expected output? What do you see instead?

Has no effect, still uses another Python

What version of the product are you using? On what operating system?

1.2.5.519. Mac OS X 10.6.1

Please provide any additional information below.

This is the same problem as
http://code.google.com/p/googleappengine/issues/detail?id=2119, but that
issue is in the wrong issue tracker. From that issue:

"There is no apparent way to run Python 2.5 with Google App Engine 
Launcher 1.2.5.519 on Mac OS X 10.6.1.

The Preferences -> Python Path has no apparent effect on what version of 
python is used to run the development server.

One would expect that setting Preferences->Python Path to 
/usr/bin/python2.5 would result in python2.5 being used to run the 
development server.

This is problematic because, perhaps among other issues, Mac OS X 10.6.x 
runs Python 2.6 by default and urllib/urllib2 does not work with the Google 
App Engine development server in Python 2.6.

The obvious workaround is to run "$ python2.5 
/usr/local/bin/dev_appserver.py path/to/app" from the command line, of 
course that means you can't use the launcher."

I made two changes, and then it worked. I don't know which change fixed it,
or even if either change fixed it. So take this with a grain of salt.

1) Added    <key>Python</key>
    <string>/opt/local/bin/python2.5</string>
to GoogleAppengineLauncher.app/Contents/Info.plist

2) Delete ~/Library/Application
Support/GoogleAppengineLauncher/Projects.plist, then reopen
GoogleAppengineLauncher and recreate project.

I have attached Info.plist (with the added key), Projects-old.plist and
Projects-new.plist

Original issue reported on code.google.com by charles....@gmail.com on 2 Oct 2009 at 1:54

Attachments:

GoogleCodeExporter commented 8 years ago
This is actually a UI bug; to save the path, you have to press "enter" inside 
the text field, 
but the UI doesn't indicate this.

I've opened 
http://code.google.com/p/google-appengine-mac-launcher/issues/detail?
id=4 to more accurately track the problem.

Original comment by jamezpol...@gmail.com on 22 Nov 2009 at 9:57

GoogleCodeExporter commented 8 years ago
dont know where to add GoogleAppengineLauncher.app/Contents/Info.plist or to 
find ~/Library/Application
Support/GoogleAppengineLauncher/Projects.plist in order to delete. obviously, 
am beginner in python and google app engine. i attempted to change python path 
with code i found on a forum in order to get google app engine to open with 
2.7. code basically broke run function and now i cant get anything to work. my 
OS is 10.5.8. thanks to anyone who wants to help me ... la stupida.

Original comment by elitzab...@gmail.com on 22 Aug 2012 at 6:36

GoogleCodeExporter commented 8 years ago
Thanks for the comment that this is a UI bug - there's no indication you need 
to press enter, so until I read this, I was mystified.

As of April 2014 this UI bug still seems to be present.

Original comment by clareslo...@gmail.com on 19 Apr 2014 at 2:50

GoogleCodeExporter commented 8 years ago
Yes this bug still exists, should it not be tracked on 
https://code.google.com/p/googleappengine/issues/list so we have a better 
chance of it being fixed?

Original comment by patr...@cloudmatters.co on 2 Dec 2014 at 10:05