Update on Latest Releases

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Update on Latest Releases

Phil Thompson-5
I've withdrawn the latest releases until I'm sure all the of the problems have been resolved.

The root cause is me not realising the inconsistencies in the way the types of signal arguments are declared in Qt. This means some signals have always been broken. I will make a new release (hopefully in a few days) when I'm sure it is no more broken than before.

Phil
_______________________________________________
PyQt mailing list    [hidden email]
https://www.riverbankcomputing.com/mailman/listinfo/pyqt
Reply | Threaded
Open this post in threaded view
|

Re: Update on Latest Releases

Florian Bruhin


On June 24, 2018 7:04:08 PM GMT+02:00, Phil Thompson <[hidden email]> wrote:
>I've withdrawn the latest releases until I'm sure all the of the
>problems have been resolved.
>
>The root cause is me not realising the inconsistencies in the way the
>types of signal arguments are declared in Qt. This means some signals
>have always been broken. I will make a new release (hopefully in a few
>days) when I'm sure it is no more broken than before.

Thanks for the update! FWIW when there's a nightly snapshot I'd be happy to run qutebrowser's testsuite against it and provide feedback.
_______________________________________________
PyQt mailing list    [hidden email]
https://www.riverbankcomputing.com/mailman/listinfo/pyqt
Reply | Threaded
Open this post in threaded view
|

Re: Update on Latest Releases

Florian Bruhin
On Sun, Jun 24, 2018 at 07:45:33PM +0200, Florian Bruhin wrote:

>
>
> On June 24, 2018 7:04:08 PM GMT+02:00, Phil Thompson <[hidden email]> wrote:
> >I've withdrawn the latest releases until I'm sure all the of the
> >problems have been resolved.
> >
> >The root cause is me not realising the inconsistencies in the way the
> >types of signal arguments are declared in Qt. This means some signals
> >have always been broken. I will make a new release (hopefully in a few
> >days) when I'm sure it is no more broken than before.
>
> Thanks for the update! FWIW when there's a nightly snapshot I'd be happy to run qutebrowser's testsuite against it and provide feedback.
I've now seen some changes in today's nightlies so I thought I'd give it
a try - however, it doesn't seem to work at all:

    >>> from PyQt5 import QtCore
    Traceback (most recent call last):
      File "<stdin>", line 1, in <module>
    ValueError: PyCapsule_GetPointer called with incorrect name

That's with PyQt5_gpl-5.11.2.dev1806252238, sip-4.19.11.dev1806251808,
GCC 8.1.1 20180531, Python 3.6.5 on Archlinux.

Just thought I'd let you know - I'll try again tomorrow :)

Florian

--
https://www.qutebrowser.org | [hidden email] (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
         I love long mails! | https://email.is-not-s.ms/

_______________________________________________
PyQt mailing list    [hidden email]
https://www.riverbankcomputing.com/mailman/listinfo/pyqt

signature.asc (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Update on Latest Releases

Phil Thompson-5
On 26/06/2018 13:00, Florian Bruhin wrote:

> On Sun, Jun 24, 2018 at 07:45:33PM +0200, Florian Bruhin wrote:
>>
>>
>> On June 24, 2018 7:04:08 PM GMT+02:00, Phil Thompson
>> <[hidden email]> wrote:
>> >I've withdrawn the latest releases until I'm sure all the of the
>> >problems have been resolved.
>> >
>> >The root cause is me not realising the inconsistencies in the way the
>> >types of signal arguments are declared in Qt. This means some signals
>> >have always been broken. I will make a new release (hopefully in a few
>> >days) when I'm sure it is no more broken than before.
>>
>> Thanks for the update! FWIW when there's a nightly snapshot I'd be
>> happy to run qutebrowser's testsuite against it and provide feedback.
>
> I've now seen some changes in today's nightlies so I thought I'd give
> it
> a try - however, it doesn't seem to work at all:
>
>     >>> from PyQt5 import QtCore
>     Traceback (most recent call last):
>       File "<stdin>", line 1, in <module>
>     ValueError: PyCapsule_GetPointer called with incorrect name
>
> That's with PyQt5_gpl-5.11.2.dev1806252238, sip-4.19.11.dev1806251808,
> GCC 8.1.1 20180531, Python 3.6.5 on Archlinux.
>
> Just thought I'd let you know - I'll try again tomorrow :)

That smells like a configuration error, maybe mismatched sips? Did you
specify the ——sip-module flag?

Phil

_______________________________________________
PyQt mailing list    [hidden email]
https://www.riverbankcomputing.com/mailman/listinfo/pyqt
Reply | Threaded
Open this post in threaded view
|

Re: Update on Latest Releases

Detlev Offenbach
Hello,

I saw the same issue when I downgraded the PyQt5 wheel from 5.11 back to 5.10.
The culprit was a leftover sip.so file in the PyQt5 directory.

Detlev

Am Dienstag, 26. Juni 2018, 19:01:05 CEST schrieb Phil Thompson:

> On 26/06/2018 13:00, Florian Bruhin wrote:
> > On Sun, Jun 24, 2018 at 07:45:33PM +0200, Florian Bruhin wrote:
> >> On June 24, 2018 7:04:08 PM GMT+02:00, Phil Thompson
> >>
> >> <[hidden email]> wrote:
> >> >I've withdrawn the latest releases until I'm sure all the of the
> >> >problems have been resolved.
> >> >
> >> >The root cause is me not realising the inconsistencies in the way the
> >> >types of signal arguments are declared in Qt. This means some signals
> >> >have always been broken. I will make a new release (hopefully in a few
> >> >days) when I'm sure it is no more broken than before.
> >>
> >> Thanks for the update! FWIW when there's a nightly snapshot I'd be
> >> happy to run qutebrowser's testsuite against it and provide feedback.
> >
> > I've now seen some changes in today's nightlies so I thought I'd give
> > it
> >
> > a try - however, it doesn't seem to work at all:
> >     >>> from PyQt5 import QtCore
> >    
> >     Traceback (most recent call last):
> >       File "<stdin>", line 1, in <module>
> >    
> >     ValueError: PyCapsule_GetPointer called with incorrect name
> >
> > That's with PyQt5_gpl-5.11.2.dev1806252238, sip-4.19.11.dev1806251808,
> > GCC 8.1.1 20180531, Python 3.6.5 on Archlinux.
> >
> > Just thought I'd let you know - I'll try again tomorrow :)
>
> That smells like a configuration error, maybe mismatched sips? Did you
> specify the ——sip-module flag?
>
> Phil
>
> _______________________________________________
> PyQt mailing list    [hidden email]
> https://www.riverbankcomputing.com/mailman/listinfo/pyqt

--
Detlev Offenbach
[hidden email]


_______________________________________________
PyQt mailing list    [hidden email]
https://www.riverbankcomputing.com/mailman/listinfo/pyqt
Reply | Threaded
Open this post in threaded view
|

Re: Update on Latest Releases

Florian Bruhin
In reply to this post by Phil Thompson-5
On Tue, Jun 26, 2018 at 06:01:05PM +0100, Phil Thompson wrote:

> On 26/06/2018 13:00, Florian Bruhin wrote:
> > On Sun, Jun 24, 2018 at 07:45:33PM +0200, Florian Bruhin wrote:
> > >
> > >
> > > On June 24, 2018 7:04:08 PM GMT+02:00, Phil Thompson
> > > <[hidden email]> wrote:
> > > >I've withdrawn the latest releases until I'm sure all the of the
> > > >problems have been resolved.
> > > >
> > > >The root cause is me not realising the inconsistencies in the way the
> > > >types of signal arguments are declared in Qt. This means some signals
> > > >have always been broken. I will make a new release (hopefully in a few
> > > >days) when I'm sure it is no more broken than before.
> > >
> > > Thanks for the update! FWIW when there's a nightly snapshot I'd be
> > > happy to run qutebrowser's testsuite against it and provide
> > > feedback.
> >
> > I've now seen some changes in today's nightlies so I thought I'd give it
> > a try - however, it doesn't seem to work at all:
> >
> >     >>> from PyQt5 import QtCore
> >     Traceback (most recent call last):
> >       File "<stdin>", line 1, in <module>
> >     ValueError: PyCapsule_GetPointer called with incorrect name
> >
> > That's with PyQt5_gpl-5.11.2.dev1806252238, sip-4.19.11.dev1806251808,
> > GCC 8.1.1 20180531, Python 3.6.5 on Archlinux.
> >
> > Just thought I'd let you know - I'll try again tomorrow :)
>
> That smells like a configuration error, maybe mismatched sips? Did you
> specify the ——sip-module flag?
Removing the virtualenv and recreating one from scratch (without
leftovers from old PyQt/sip installs) helped. Thanks Phil and Detlev!

FWIW the current nightlies (PyQt5_gpl-5.11.2.dev1806261018,
sip-4.19.11.dev1806260915) work without any issues for me so far! :)

Florian

--
https://www.qutebrowser.org | [hidden email] (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
         I love long mails! | https://email.is-not-s.ms/

_______________________________________________
PyQt mailing list    [hidden email]
https://www.riverbankcomputing.com/mailman/listinfo/pyqt

signature.asc (849 bytes) Download Attachment