> Date: Sun, 03 Oct 2010 21:32:32 -0700 > From: Dan Helfman <[email protected]> > Subject: Re: [SEAPY] Py2exe help? > To: [email protected] > Message-ID: <[email protected]> > Content-Type: text/plain; charset=windows-1252; format=flowed > > On 10/03/2010 08:49 PM, David Goldsmith wrote: >> Hi seapiggies! Sorry for posting this here, but I'm being stonewalled >> by the py2exe-users list (I subscribed to the list, including having >> received confirmation thereof, but my posts keep getting bounced back >> w/ "You are not allowed to post to this list." I emailed >> py2exe-users-owner a week ago and haven't heard a thing!) :-( >> >> Anyway, I think my question is rather simple: I?m py2exe-ing a >> Tk-utilizing GUI script, which also writes stuff to stdout/stderr. So >> far, no problems, but what?s the preferred way to have my app >> instantiate a console and direct stdout/stderr to it? os.spawnl? >> Something fancier? Thanks! > > Hi David, > > Usually, py2exe apps don't write anything to a console, but rather to a > log file. You might find this page on py2exe stderr redirection helpful: > http://www.py2exe.org/index.cgi/StderrLog > > Dan
Hi, Dan, thanks for your reply. You say "usually": is this a euphemism for "necessarily always"? The person I'm writing the script for is skeptical in the extreme and wants "live" feedback as to precisely what the app is doing. (If it helps: I'm automating a telnet session the guy for whom I'm writing it is used to doing manually; they're not accustomed to Python around here, plus it's of primary importance that everything go "exactly right," so he wants to see each telnet command issued and each returned result.) Thanks again, DG
