Re: [PyKDE] Re: Signal destroyed() not emitted for QWidget

2006-02-14 Thread Giovanni Bajo
Phil Thompson <[EMAIL PROTECTED]> wrote: >> Thanks. But why does it work for QObject and not for QWidget? > > I don't know - you'll have to read the code of the QObject dtor. I'm just > happy that C++ demonstrates the same behaviour. Ah, found it! QObject's dtor does emit destroyed() and then del

Re: [PyKDE] Re: Signal destroyed() not emitted for QWidget

2006-02-14 Thread Phil Thompson
On Tuesday 14 February 2006 4:28 pm, Giovanni Bajo wrote: > Phil Thompson <[EMAIL PROTECTED]> wrote: > > I think this is the way Qt works when the receiver is a child of the > > sender. > > > When PyQt3 makes a connection to a Python callable it creates a proxy > > QObject that is actually connecte

[PyKDE] Auto-disconnection of signals broken?

2006-02-14 Thread Giovanni Bajo
Phil, Using PyQt snapshot-20051212 and SIP snapshot-20051212: --- from qt import * app = QApplication([]) o = QObject(None) w = QWidget(None) QObject.connect(o, PYSIGNAL("FOO"), w.update) o.emit(PYSIGNAL("FOO"), ()) w.deleteLater() o

[PyKDE] Re: Signal destroyed() not emitted for QWidget

2006-02-14 Thread Giovanni Bajo
Phil Thompson <[EMAIL PROTECTED]> wrote: > I think this is the way Qt works when the receiver is a child of the sender. > When PyQt3 makes a connection to a Python callable it creates a proxy > QObject that is actually connected to the sender. To make sure the proxy > doesn't leak memory it is mad

[PyKDE] Re: Signal destroyed() not emitted for QWidget

2006-02-14 Thread Phil Thompson
On Tuesday 14 February 2006 2:45 pm, Giovanni Bajo wrote: > Phil, > > Using PyQt snapshot-20051212 and SIP snapshot-20051212, I found this bug: > > > from qt import * > > app = QApplication([]) > > def testDestruction(cls): > def foo(o): >

Re: [PyKDE] Run program as root

2006-02-14 Thread Tina Isaksen
Hans-Peter Jansen wrote: On 2/13/06, Tina Isaksen <[EMAIL PROTECTED]> wrote: Noob question: As a learning project I'm making some system tool frontends for kde (using Qt), but for the life of me I can't find how to make a script run as root (superuser)... and prompt for the root password f

[PyKDE] Signal destroyed() not emitted for QWidget

2006-02-14 Thread Giovanni Bajo
Phil, Using PyQt snapshot-20051212 and SIP snapshot-20051212, I found this bug: from qt import * app = QApplication([]) def testDestruction(cls): def foo(o): print "destroyed:", o destroyed.append(o) destroyed = []

Re: [PyKDE] Run program as root

2006-02-14 Thread Hans-Peter Jansen
Am Dienstag, 14. Februar 2006 09:45 schrieb Patrick Stinson: > Even though this is more of a python question than a pykde question, > > #!/bin/sh > > # wrapper shell script > sudo /path/to/python $@ This will only work with sudo configured to not ask for a password. Otherwise you need to run it i

Re: [PyKDE] Run program as root

2006-02-14 Thread Patrick Stinson
Even though this is more of a python question than a pykde question, #!/bin/sh # wrapper shell script sudo /path/to/python $@ On 2/13/06, Tina Isaksen <[EMAIL PROTECTED]> wrote: Noob question:As a learning project I'm making some system tool frontends for kde(using Qt), but for the life of me I

[PyKDE] Run program as root

2006-02-14 Thread Tina Isaksen
Noob question: As a learning project I'm making some system tool frontends for kde (using Qt), but for the life of me I can't find how to make a script run as root (superuser)... and prompt for the root password first of course? Thanks Tina ___ PyKD

Re: [PyKDE] PyQt(4) development environment for windows

2006-02-14 Thread V. Armando Sole
At 14:14 13/02/2006 +0100, Andreas Pakulat wrote: Did I say that I think there's no free Qt3? What I said was: There's no free PyQt3 for Windows, unless the license of the free PyQt3 for *nix allows to use it under Windows with the free Qt3 port (and that this actually works). However from the w