pythonw freezes with print output

T

Thomas Kwapich

Hi,

I'm developing a wxpython application under windows 2000.
If I start it with pythonw.exe (without dos window) it freezes
after some time depending on the amount of print output it generates.
On the other hand if I start it with python.exe (the dos window is shown)
it is stable.
Reducing the print output to zero makes it even stable when started with
pythonw.

(I tried to debug it with SciTe but it doesn't crash with it altough
SciTe starts it with pythonw)

Any ideas why this happens?

Best regards

Thomas
 
T

Thomas Heller

Thomas Kwapich said:
Hi,

I'm developing a wxpython application under windows 2000.
If I start it with pythonw.exe (without dos window) it freezes
after some time depending on the amount of print output it generates.
On the other hand if I start it with python.exe (the dos window is shown)
it is stable.
Reducing the print output to zero makes it even stable when started with
pythonw.

(I tried to debug it with SciTe but it doesn't crash with it altough
SciTe starts it with pythonw)

Any ideas why this happens?

It is my experience (with Win2k and XP, and Python 2.2 at least) that
you get an IOError after writing 4096 bytes (or so) to sys.stdout.

You should probably redirect sys.stdout and sys.stderr to a file, or a
file-like object, otherwise you won't see any output or any tracebacks.

(It may work in SciTe because SciTe catches the output of the program itself?)

Thomas
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

No members online now.

Forum statistics

Threads
473,744
Messages
2,569,482
Members
44,901
Latest member
Noble71S45

Latest Threads

Top