[PyQt] Re: pykde crash on debian etch / import kparts or khtml
Jim Bublitz wrote: It crashes here too (not on Debian). It appears to be related to the 'newItems' signal - that's where the backtrace indicates the crash is originating. I have no idea what the cause is, but I think you can achieve the same thing with the two changes below, and with those changes it works here. From looking at the comments in the KDE h files, it seems like there might be some kind of timing issues related to the signals, but I have no idea why importing other modules would trigger the problem. That was exactly my conclusion. I did the same thing by digging (quite superficialy i confess) in the source and i have seen the same comments. I'd like to understand what importing those specific modules trigger the problem. I hope i'm gonna have some time to look into it. Many thanks for your answer. Jb ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Eric3 issue: importing modules with the same name as an Eric module
Detlev wrote: > Over here it failed to start the debug client because of an > ImportError. It cannot find the file, if the long import is given. Hi Detlev, I worked on it over the weekend on a different flavour of Linux, and I noticed the same issue you do. Apparently different distros package Eric in different ways. On Ubuntu (and presumably Debian) the fix works with "from DebugClients.Python.Config import ...", while on Gentoo it requires "from eric3.DebugClients.Python.Config import ...". Since the Eric documentation DOES refer to the DebugClients package as 'eric3.DebugClients' (see documentation file index-eric3.DebugClients.html), I'll go and assert that it's probably Ubuntu/Debian being silly and packaging stuff their own way here. Meaning that the fix should go: -from Config import ConfigVarTypeStrings +from eric3.DebugClients.Python.Config import ConfigVarTypeStrings ... And let Debian and friends fix their packaging. Once more, however, the same treatment should probably be applied to the other packages that the debug client imports locally. Or if you'd rather, I can try to look into how feasible it'd be to create a custom import hook that would isolate the debugger's imports from that of the user code. I, uh, I hope I'm not bothering you with my repeated attention to this admittedly minor issue? Thanks, -- S. ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Eric3 issue: importing modules with the same name as an Eric module
On Montag, 1. Oktober 2007, Sundance wrote: > Detlev wrote: > > Over here it failed to start the debug client because of an > > ImportError. It cannot find the file, if the long import is given. > > Hi Detlev, > > I worked on it over the weekend on a different flavour of Linux, and I > noticed the same issue you do. > > Apparently different distros package Eric in different ways. > > On Ubuntu (and presumably Debian) the fix works with "from > DebugClients.Python.Config import ...", while on Gentoo it > requires "from eric3.DebugClients.Python.Config import ...". > > Since the Eric documentation DOES refer to the DebugClients package > as 'eric3.DebugClients' (see documentation file > index-eric3.DebugClients.html), I'll go and assert that it's probably > Ubuntu/Debian being silly and packaging stuff their own way here. > > Meaning that the fix should go: > > -from Config import ConfigVarTypeStrings > +from eric3.DebugClients.Python.Config import ConfigVarTypeStrings > > ... And let Debian and friends fix their packaging. > > Once more, however, the same treatment should probably be applied to the > other packages that the debug client imports locally. > > Or if you'd rather, I can try to look into how feasible it'd be to > create a custom import hook that would isolate the debugger's imports > from that of the user code. > > I, uh, I hope I'm not bothering you with my repeated attention to this > admittedly minor issue? Actually it is not a minor issue. If possible I would try the import hook approach. Would you take this task? Regards, Detlev Btw, your email address gives errors (not deliverable). -- Detlev Offenbach [EMAIL PROTECTED] ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
