On Mon, 7 Jan 2019 at 21:11, Martin Dobias wrote:
>
> Hi Nyall
>
> I have seen that too with other QGIS registries, but I am not sure if
> it is actually broken in SIP or if this should be simply handled in a
> different way.
>
> My understanding is that SIP for an object has the "c++ part" and
>
Hi Martin
On 07.01.19 13:22, Martin Dobias wrote:
Hi Matthias
On Mon, Jan 7, 2019 at 12:34 PM Matthias Kuhn wrote:
Are you convinced that the proper solution will be a /ReleaseReference/
annotation?
I am not convinced, but for now I do not have a better idea :-)
I agree that the virtual
Hi Matthias
On Mon, Jan 7, 2019 at 12:34 PM Matthias Kuhn wrote:
>
> Are you convinced that the proper solution will be a /ReleaseReference/
> annotation?
I am not convinced, but for now I do not have a better idea :-)
I agree that the virtual destructors could automatically release that
held
Hi all,
I have observed the same in the past.
This explanation sounds very reasonable, Martin.
Are you convinced that the proper solution will be a /ReleaseReference/
annotation?
I would assume that the current information is sufficient for sip /
sipify to generate proper bindings without
Hi Nyall
I have seen that too with other QGIS registries, but I am not sure if
it is actually broken in SIP or if this should be simply handled in a
different way.
My understanding is that SIP for an object has the "c++ part" and
"python part". If we do not deal with subclasses, things seem to
On 1/4/19 9:45 AM, Alessandro Pasotti wrote:
>
> It's not just you, this is what I see when running your code:
>
> WTFFF!!!
>
> Found PyQt5 version: 5.11.2
>
> Found SIP version: 4.19.13
Same issue here with slightly newer PyQt5: 5.11.3 and same SIP version...
No Clue, sorry :(
Richard
It's not just you, this is what I see when running your code:
WTFFF!!!
Found PyQt5 version: 5.11.2
Found SIP version: 4.19.13
On Thu, Jan 3, 2019 at 8:19 AM Nyall Dawson wrote:
> Hi list,
>
> I'm at my wits end here, fighting with a sip issue I can't solve. And
> honestly, I'm
Hi list,
I'm at my wits end here, fighting with a sip issue I can't solve. And
honestly, I'm starting to think maybe there's something completely
broken in sip. (Or at least, in the version 4.19.7 provided by my
distro).
Here's what I'm currently hitting:
The validity check registry added this
