[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pykde
Subject:    Re: [PyQt] Potential API break in PyQt4 snapshot
From:       Davide Pesavento <pesa () gentoo ! org>
Date:       2016-06-12 11:14:15
Message-ID: CADfzvvZEW5-Dipsmjp1UnvN_UjdXHM-p2rp2OVcMj=vh8wK75g () mail ! gmail ! com
[Download RAW message or body]

On Fri, Jun 10, 2016 at 3:16 PM, Phil Thompson
<phil@riverbankcomputing.com> wrote:
> On 1 Jun 2016, at 12:18 am, Davide Pesavento <pesa@gentoo.org> wrote:
>>
>> On Mon, May 30, 2016 at 9:25 PM, Davide Pesavento <pesa@gentoo.org> wrote:
>>> A Gentoo Linux user has encountered a compilation failure while
>>> building KDE4's kate editor (version 4.14.3) against the latest PyQt4
>>> snapshot (version 4.12.dev1605051544).
>>>
>>> Is this an unintentional API change in PyQt4, or is kate using
>>> undocumented/private APIs? Or something else?
>>>
>>
>> So, the following code from qobject.sip is new in PyQt4-4.12.dev
>>
>>        #if defined(SIP_PROTECTED_IS_PUBLIC)
>>            (sipSelfWasArg ? sipCpp->QObject::connectNotify(sig) :
>> sipCpp->connectNotify(sig));
>>        #else
>>            sipCpp->sipProtectVirt_connectNotify(sig);
>>        #endif
>>
>> The compiler complains about sipProtectVirt_connectNotify, which means
>> SIP_PROTECTED_IS_PUBLIC is *not* defined. This is consistent with the
>> fact that sip is invoked without the -P option to generate kate
>> bindings.
>>
>> Does this ring any bells?
>
> Should be fixed in tonight's snapshot.
>

Confirmed fixed in 4.12.dev1606101416. Thanks.

Davide
_______________________________________________
PyQt mailing list    PyQt@riverbankcomputing.com
https://www.riverbankcomputing.com/mailman/listinfo/pyqt
[prev in list] [next in list] [prev in thread] [next in thread]