Re: [Pythoncard-users] Standalone PythonCard applications & no console

[XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX]

On 26/8/06 22:02, Kevin Altis wrote:
> 
> On Aug 26, 2006, at 6:31 AM, XXXXXXXXXXX wrote:
> 
>> I'm still building Windows EXEs via the Mcmillan installer that I set-up
>> quite a while ago (I'll get standaloneBuilder one of these days!) and I
>> still use that old debugging technique, the print statement, all the 
>> time.
>>
<snip>
> 
> That sounds more like a bug in McMillan to me. Have you tried using the 
> updated pyInstaller instead? Maybe it is changing where sys.stdout and 
> sys.stderr go? You could add some fields to your application and dump 
> the values for both of those. You could also assign some other file-like 
> object to sys.stdout. You could make your own that even dumps text on a 
> write to a hidden TextArea field which might be a temporary workaround 
> until you figure out the real problem. Alternatively, assign a real file 
> handle to sys.stdout or sys.stderr and capture the specific tracebacks 
> that way. Just a few ideas to help debug the problem.
> 

Thanks Kevin....I'll have to get the latest pyInstaller and find out if 
that makes a diference. In the meantime I've commented out the print 
statements and left the code in place to write the strings to a text file.

-- 
XXXXXXXXXXX