On Wed, Oct 24, 2007 at 05:25:09PM +0900, Michal Čihař wrote: > On Wed, 24 Oct 2007 17:49:11 +0930 > Ron <[EMAIL PROTECTED]> wrote: > > Well Wammu does depend on python-wxgtk2.6 and 'import wx' fails. I > simply do not see how problem could be in Wammu. > > > You didn't even bother to simply try: > > > > $ python > > Python 2.4.4 (#2, Aug 16 2007, 02:03:40) > > [GCC 4.1.3 20070812 (prerelease) (Debian 4.1.2-15)] on linux2 > > Type "help", "copyright", "credits" or "license" for more information. > > >>> import wx > > >>> > > Because I don't see any point in trying this, Wammu does nothing > different.
Well clearly something is different as wx installed from sid does not do this on its own -- so it would seem to be an issue with either wammu or the user's system. I presume you also can't reproduce this, even with wammu? > > Which in the absence of other evidence would seem to rule out > > python-wxgtk2.6 being "somehow broken" and the cause of this. > > I was just hoping that you could give some hits how to resolve problem > with not working wxPython. Sorry to bother you. You can always ask me for input without reassigning the bug. Without verification that just makes busy-work for the both of us. It's sounding like a local problem, so the real issue is how did that happen, and what, if anything, can we do to prevent it in future. I don't know enough about wammu or its packaging to really answer that myself. If you find something that really is a wx problem then do bounce it back to me, but so far I don't see any hint of that being the case... Cheers, Ron -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
