On Nov 9, 2008, at 4:42 PM, Steve Holden wrote:
I usually only get around to reading the list when I'm having a
problem I can't figure out. <blush>.
Simply too busy most of the time.
OK, I didn't see subprocess. I'll give that a whirl. In the meantime,
I did find that wxPython has wx.Execute, and it seems to be working,
although it prints some odd messages when running under OS X. Thanks!
-- Ed Leafe
Ed! Good to see you on c.l.py!
problem I can't figure out. <blush>.
Simply too busy most of the time.
a) Try using the subprocess module
b) Use *.pyw programs to ensure no console window is created.
b) Use *.pyw programs to ensure no console window is created.
OK, I didn't see subprocess. I'll give that a whirl. In the meantime,
I did find that wxPython has wx.Execute, and it seems to be working,
although it prints some odd messages when running under OS X. Thanks!
-- Ed Leafe