Re: [PyKDE] pyqt/mysqld thread deadlock

2003-01-01 Thread Kaleb Pederson
On Wednesday 01 January 2003 11:40 am, you wrote: On Wednesday 01 January 2003 5:58 pm, Kaleb Pederson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 snip It turns out, however, that the thread locks in the middle of my run() call and never completes. I'm cross-posting

Re: [PyKDE] pyqt/mysqld thread deadlock

2003-01-01 Thread Kaleb Pederson
On Wednesday 01 January 2003 12:50 pm, you wrote: Phil Thompson [EMAIL PROTECTED] writes: You could try instrumenting lock_import(), or replace the mysqldb calls with code that still does the imports but nothing else. Alternatively, you could also ask your debugger for a stack trace for

Re: [PyKDE] pyqt/mysqld thread deadlock

2003-01-01 Thread Kaleb Pederson
On Wednesday 01 January 2003 01:42 pm, Martin v. Löwis wrote: Kaleb Pederson wrote: (gdb) thread 1 #0 0x4024b1be in select () from /lib/libc.so.6 [...] #16 0x080a81d2 in PyImport_ImportModuleEx (name=0x818a924 gem.src.gui.gui, globals=0x8145154, locals=0x8145154, fromlist=0x8114484

Re: [PyKDE] pyqt/mysqld thread deadlock

2003-01-01 Thread Kaleb Pederson
On Wednesday 01 January 2003 01:42 pm, Martin v. Löwis wrote: Kaleb Pederson wrote: (gdb) thread 1 #0 0x4024b1be in select () from /lib/libc.so.6 See the source of PyImport_ImportModuleEx. It acquires the import lock, so you are holding the import lock while QApplication_exec_loop

Re: [PyKDE] Opinions on pyuic Custom Widget Support

2002-12-14 Thread Kaleb Pederson
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I don't have a better suggestion at the time. The way it currently works is very intuitive. Without looking through the documentation, I assumed that it would work that way and when I added custom widgets to my programs everything just worked. I

RE: [PyKDE] destructor not getting called?

2002-11-08 Thread Kaleb Pederson
On Friday 08 November 2002 07:42, Kaleb Pederson wrote: On Thursday 07 November 2002 10:14 pm, Boudewijn Rempt wrote: snip Hmmm... What I do is to create a Python class with the settings as member variables. That makes it easier. But still, the Qt documentation says: A typical usage pattern

Re: [PyKDE] destructor not getting called?

2002-11-07 Thread Kaleb Pederson
On Thursday 07 November 2002 10:14 pm, Boudewijn Rempt wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 It might be my Java heritage, but I've never trusted destructors... Couldn't you just connect the LastWindowClosed signal to the save method? Why I personally to is to write the

Re: [PyKDE] BUG - disconnect

2002-11-06 Thread Kaleb Pederson
On Wednesday 06 November 2002 04:00 pm, Phil Thompson wrote: snip Thanks. Although it isn't usually necessary, it will be nice to have. There is a bug in PyQt with respect to connections being removed when the associated object has been deleted. But I'll try to post some example code

Re: [PyKDE] BUG - disconnect

2002-11-04 Thread Kaleb Pederson
On Sunday 03 November 2002 12:13 pm, Phil Thompson wrote: On Tuesday 29 October 2002 12:46 am, Kaleb Pederson wrote: Disconnect doesn't seem to work as expected. snip which are all very similar to the documentation examples. SIP can't seem to tell which method really should be called

Re: [PyKDE] BUG - disconnect

2002-11-04 Thread Kaleb Pederson
Thanks. Although it isn't usually necessary, it will be nice to have. There is a bug in PyQt with respect to connections being removed when the associated object has been deleted. But I'll try to post some example code within the week. Basically, if I create a parentless object and connect

Re: [PyKDE] BUG - disconnect

2002-11-04 Thread Kaleb Pederson
On Monday 04 November 2002 05:59 am, Kaleb Pederson wrote: Thanks. Although it isn't usually necessary, it will be nice to have. There is a bug in PyQt with respect to connections being removed when the associated object has been deleted. But I'll try to post some example code within

RE: [PyKDE] Python references and the GC

2002-10-30 Thread Kaleb Pederson
Schönenberg [mailto:micke;ratthing-b3cd.strakt.com] On Behalf Of Mikael Schönenberg Sent: Wednesday, October 30, 2002 12:54 AM To: Kaleb Pederson Cc: [EMAIL PROTECTED] Subject: Re: [PyKDE] Python references and the GC On Tue, 29 Oct 2002, Kaleb Pederson wrote: I have a class similar to the below

[PyKDE] Python references and the GC

2002-10-29 Thread Kaleb Pederson
I have a class similar to the below that keeps a reference to itself so that it doesn't get garbage collected. class sample(qdialog): def __init__(...): qwidget.__init__(...) self._keep = self ... def closeEvent(self,event):

[PyKDE] BUG - disconnect

2002-10-28 Thread Kaleb Pederson
Disconnect doesn't seem to work as expected. Per the Qt documentation (qobject.html#disconnect) I should be able to disconnect signals as follows. I've tried various methods: def sigDiscon(self): self.disconnect() # Test 1 #QObject.disconnect(self,0,0,0) # Test 2 - or

Re: [PyKDE] Borderless Window with SuSE 8.0 Linux

2002-09-24 Thread Kaleb Pederson
Make sure that your parent widget work doesn't enforce certain window flags. Depending on the parent widget, it doesn't matter what flags you pass in. This works for me: splash = SplashScreen.SplashScreen(None, splash, Qt.WDestructiveClose | Qt.WStyle_Customize | Qt.WStyle_NoBorder |

Re: [PyKDE] ANNOUNCING PyQwt-sip34_20020807 - some problems on Win32

2002-09-19 Thread Kaleb Pederson
On Thursday 19 September 2002 01:01 am, Phil Thompson wrote: I am happy to send you the the binary PyQwt windows installer and zip builds for the Qt3.0.5 commercial if you want to put them on your website. For a binary-only release, according the the commercial qt license, I see no