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

[John Jackson]

That was going to be my next attempt. I liked the callbacks in  
wxProcess.

Running the demo on the Mac this morning, I noticed this showed up in  
the demo. It still ran, but it gave the error message:

> Debug: wxMacExecute Bad bundle: python
> Debug: pid=23179
> Debug: Successfully added notification to the runloop
> OnExecuteBtn: "python -u data/echo.py" pid: 23179
> OnSendText: "test"
> OnCloseStream
> Debug: Process ended
> OnProcessEnded, pid:23179,  exitCode: 0

Do you use the popen commands, or the newer subprocess module?

On Mar 12, 2008, at 9:07 AM, Kevin Ollivier wrote:

> Hi John,
>
> I'm not sure what's going on with wxProcess, but have you tried  
> working with the Python classes for launching new processes? I  
> think a lot of people use the built in Python modules (I know I  
> do...), which could be why we haven't come across this before.
>
> Regards,
>
> Kevin
>
> On Mar 11, 2008, at 5:26 PM, John Jackson wrote:
>
>> I ran the same code under Windows, and it worked fine. (Well, at  
>> least as fine as VirtualPC works...) So, it's a Mac problem...
>>
>> On Mar 11, 2008, at 12:08 PM, John Jackson wrote:
>>
>>> I've been trying to use wx.Process to launch a Django from a  
>>> wxPython application with no luck.
>>>
>>> What I see in my log are messages such as
>>>
>>> 11:36:46: Starting server with command:
>>> /Library/Frameworks/Python.framework/Versions/Current/bin/python  
>>> ~/Source/Mine/DjangoTest/mysite/manage.py runserver
>>> 11:36:46: Debug: wxMacExecute Bad bundle: /Library/Frameworks/ 
>>> Python.framework/Versions/Current/bin/python
>>> 11:36:46: Debug: pid=22933
>>> 11:36:46: Debug: Successfully added notification to the runloop
>>> 11:36:46: DjangoStarter: serverPID "22933" started.
>>> 11:36:46: Debug: Process ended


______________
John Jackson