Differences between revisions 4 and 5
Revision 4 as of 2004-06-17 12:19:15
Size: 1057
Editor: td9091995
Comment: by timo (at) eda-solutions.de
Revision 5 as of 2004-06-17 12:22:38
Size: 1107
Editor: td9091995
Comment:
Deletions are marked like this. Additions are marked like this.
Line 20: Line 20:
<PRE>
Line 30: Line 30:
</PRE>
Line 31: Line 32:
[Added by timo (at) eda-solutions.de]

A GTK application I made has unimported errors. I used the option 'windows', but the console window gets opened when getting an error. And maybe a tip, when closing the program it should be optional whether or not it warns for errors.

Mark Baas <m.baas _at_ zarb.org>

You can always redirect where the errors go with the sys module. sys.stderr = StringIO.StringIO() will redirect error messages to a string in your program that no one will ever see.

A better option is a log file, then they can see the errors if the want to but don't have to sys.stderr = open("logfile.txt","w")

if you want to redirect print statements as well, point sys.stdout to some other file

To avoid runtime errors on closing the windows executable, it may help to suppress all output and modify py2exe/boot_common.py to <PRE> if sys.frozen == "windows_exe" :

  • class Blackhole(object):
    • softspace = 0 def write(self, text):
      • pass
    sys.stdout = Blackhole() sys.stderr = Blackhole() del Blackhole

del sys </PRE>

[Added by timo (at) eda-solutions.de]

GuiApps (last edited 2015-04-29 09:11:14 by JimmyRetzlaff)