On Tue, 2011-04-19 at 08:08 +0100, Phil Thompson wrote:
> On Tue, 19 Apr 2011 08:46:13 +0200, Benjamin Kloster
> wrote:
> > On Mon, 2011-04-18 at 22:18 +0100, Phil Thompson wrote:
> >> On Mon, 18 Apr 2011 14:07:13 +0200, Benjamin Kloster
> >> wrote:
> >> > Hi everyone,
> >> > twice now I've stumb
On Tue, 19 Apr 2011 08:46:13 +0200, Benjamin Kloster
wrote:
> On Mon, 2011-04-18 at 22:18 +0100, Phil Thompson wrote:
>> On Mon, 18 Apr 2011 14:07:13 +0200, Benjamin Kloster
>> wrote:
>> > Hi everyone,
>> > twice now I've stumbled over a subtle bug when subclassing QObject.
>> > When
>> > the get
On Mon, 2011-04-18 at 22:18 +0100, Phil Thompson wrote:
> On Mon, 18 Apr 2011 14:07:13 +0200, Benjamin Kloster
> wrote:
> > Hi everyone,
> > twice now I've stumbled over a subtle bug when subclassing QObject. When
> > the getter of a python property raises an AttributeError for any
> > attribute o
On Mon, 18 Apr 2011 14:07:13 +0200, Benjamin Kloster
wrote:
> Hi everyone,
> twice now I've stumbled over a subtle bug when subclassing QObject. When
> the getter of a python property raises an AttributeError for any
> attribute or object, PyQt seems to reraise this error improperly,
> clearing th
Hi everyone,
twice now I've stumbled over a subtle bug when subclassing QObject. When
the getter of a python property raises an AttributeError for any
attribute or object, PyQt seems to reraise this error improperly,
clearing the traceback and often reporting a false object type and
attribute name.
