[wxpython-users] Re: ANN: Tobu 0.5.0

AK andrei.avk at gmail.com
Mon Apr 14 10:18:24 PDT 2008


Robin Dunn wrote:
> AK wrote:
>> Peter Damoc wrote:
>>> You intuition is very good!
>>> The quickest workaround is to use the logging module.
>>> It already implemented all that you need complete with custom level 
>>> reporting and custom targets for reports.
>> Do you know the reason behind this problem? I'm curious because it's 
>> an odd thing to do
>> where on output to stdout when there's no stdout, things would just 
>> stop working.. is
>> stdout mapped to something else? I'd just expect it to silently 
>> disappear when stdout
>> is not present.. but I'm sure there's a good reason for it.
>>
>
> There is a stdout for X apps started from the GUI, it is inherited 
> from the parent process just like when you start from a terminal 
> session.  In this case however the parent process is probably (part 
> of) the desktop environment, which was started by the X server when it 
> initialized itself.  So the stdout/stderr are probably either the 
> system console that started X, or a file that X's output was 
> redirected to when you logged in, such as ~/.xsession*
>
Thanks for the answers! In this case I ran into it in Windows and it's a 
python
bug according to 
http://www.py2exe.org/index.cgi/Py2ExeSubprocessInteractions
(it does not apply just to py2exe but when you run .pyw without any 
terminal),
and the fix is to redirect stdout and stderr.

-- 
ak
Tobu | http://tobu.lightbird.net/ | Freeform DB / Tagger / PIM
Python-by-Example | http://pbe.lightbird.net/ | Guide to LibRef



More information about the wxpython-users mailing list