commands_test using wrong python interpreter

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Have clean python 2.6 as default python interpreter (/usr/lib/python)
2. Install all your your stuff with GAE SDK and google-app-engine-django 
into python 2.5 (or some virtual environment)
3. run $ python2.5 manage.py test 

What is the expected output? What do you see instead?
I would expect the CommandsTest pass.
Instead I get this error:

FAIL: Tests the diffsettings command.
----------------------------------------------------------------------
Traceback (most recent call last):
  File 
"/home/tarpas/workspace/bidforfix/appengine_django/tests/commands_test.py", 
line 141, in testDiffSettings
    self.assertCommandSucceeds("diffsettings")
  File 
"/home/tarpas/workspace/bidforfix/appengine_django/tests/commands_test.py", 
line 119, in assertCommandSucceeds
    (command, rc, tempname))
AssertionError: diffsettings did not return successfully (rc: 1): Output in 
/tmp/tmpn5Ko6k

---- And a couple of similar errors.

What version of the product are you using? On what operating system?
r100, python 2.5, SDK 1.3.3

Please provide any additional information below.
manage.py chooses /usr/bin/python when called from commands_test, instead 
of the interpreter which is executing commands_test
See attached diff for possible solution.

Original issue reported on code.google.com by tibor.arpas on 16 May 2010 at 2:47

Attachments:

• commands_test.diff

[GoogleCodeExporter]

The diff looks acceptable thanks.

Have you signed the CLA as described in the readme file.

Original comment by m...@google.com on 8 Jun 2010 at 11:41

• Changed state: Accepted

[GoogleCodeExporter]

Yes, I have signed it. tibor.arpas at gmail.com

Original comment by tibor.arpas on 8 Jun 2010 at 12:06

[GoogleCodeExporter]

Fixed in r104. Thanks for the patch.

Original comment by m...@google.com on 8 Jun 2010 at 2:15

• Changed state: Fixed