[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#511218: marked as done (python-wxgtk2.8: Using wx.LogStderr stops python from using stderr)

Your message dated Thu, 6 Aug 2009 22:36:19 -0700
with message-id <20090807053619.GB28475@jade.home>
and subject line Re: python-wxgtk2.8: Using wx.LogStderr stops python from using stderr
has caused the Debian Bug report #511218,
regarding python-wxgtk2.8: Using wx.LogStderr stops python from using stderr
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
511218: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=511218
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: python-wxgtk2.8
Version: 2.8.7.1-1.1
Severity: normal


Using the logging facility from wxwindows to log to stderr stops python
from using stderr inside callbacks/code called by wx.

When a python function is called by wxwindows code and tries to write to
sys.stderr (f.e. to print an exception traceback), nothing goes into
stderr if there was at least one message logged to stderr by wxwindows.

Example:

#v+
import wx
import sys

wx.LogMessage('This message stops tracebacks.')

class MyApp(wx.App):
    def OnInit(self):
        print >>sys.stderr, 'This message will not show, same with the following traceback'
        raise Exception

MyApp().MainLoop()
#v-

It is enough to comment out the 'wx.LogMessage()' statement to get both
the message and the traceback on stderr.

I see the same behaviour on my Ubuntu 8.10 box.


-- System Information:
Debian Release: 5.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
Locale: LANG=pl_PL, LC_CTYPE=pl_PL (charmap=ISO-8859-2)
Shell: /bin/sh linked to /bin/bash

Versions of packages python-wxgtk2.8 depends on:
ii  libc6                        2.7-18      GNU C Library: Shared libraries
ii  libgcc1                      1:4.3.2-1.1 GCC support library
ii  libstdc++6                   4.3.2-1.1   The GNU Standard C++ Library v3
ii  libwxbase2.8-0               2.8.7.1-1.1 wxBase library (runtime) - non-GUI
ii  libwxgtk2.8-0                2.8.7.1-1.1 wxWidgets Cross-platform C++ GUI t
ii  python                       2.5.2-3     An interactive high-level object-o
ii  python-central               0.6.8       register and build utility for Pyt
ii  python-wxversion             2.6.3.2.2-3 wxWidgets Cross-platform C++ GUI t

python-wxgtk2.8 recommends no packages.

Versions of packages python-wxgtk2.8 suggests:
pn  python-xml                    <none>     (no description available)
pn  wx2.8-doc                     <none>     (no description available)
pn  wx2.8-examples                <none>     (no description available)

-- no debconf information

----------------------------------------------------------------------
Szef przynudza? Zagraj sobie! 
Kliknij >>  http://link.interia.pl/f200e

--- End Message ---
--- Begin Message --- 
Hi,

unfortunately upstream thinks that it's your job (as the app
developer) to work around this problem, so I am closing the
Debian bug.

here's what they said: http://trac.wxwidgets.org/ticket/11077

Good luck,
Ryan

-- 
_________________________
Ryan Niebur
ryanryan52@gmail.com

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: