[wxPython-mac] Problems with wx.Process & wx.Execute

[John Jackson]

On Mar 12, 2008, at 4:54 PM, Robin Dunn wrote:

> John Jackson wrote:
>> As usual, Robin nailed it. :)
>> The command below works from the command line, which suggested  
>> that Robin's hunch was correct.
>> In the process demo, I modified the command line to run
>> python -c "import sys; sys.stdout.write('%s\n%s' % (sys.version,  
>> sys.path))"
>> When I run it, I see that I'm running 2.3.5, instead of 2.5.1:
>> 2.3.5 (#1, Mar 20 2005, 20:38:20)
>> [GCC 3.3 20030304 (Apple Computer, Inc. build 1809)]
>> ...and all the elements in the sys.path are from 2.3. So, of  
>> course that won't work. That's why Django dies immediately.
>
> The first python found on your default PATH is /usr/bin/python.
>

I had anticipated that, which is why I used the full path "/Library/ 
Frameworks/Python.framework/Versions/Current/bin/python".

However, what I was doing wrong was that the expansion of ~ doesn't  
work:

/Library/Frameworks/Python.framework/Versions/Current/bin/python -u ~/ 
Source/Mine/DjangoTest/mysite/manage.py runserver

works on the command line, but not on the wxExecute. The error  
message is that the error code is 2, which probably means the command  
never got off the ground.

Now that I have that fixed, it can start a Django server.... getting  
all the text back is being a little cranky.

Thanks!

______________
John Jackson