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

List:       pykde
Subject:    Re: [PyQt] qscintilla (and others) and private sip modules
From:       Phil Thompson <phil () riverbankcomputing ! com>
Date:       2018-08-26 15:13:34
Message-ID: 5A9E3616-E9F6-4E1C-AA5F-76E7A327A184 () riverbankcomputing ! com
[Download RAW message or body]

On 26 Aug 2018, at 3:57 pm, Rex Dieter <rdieter@math.unl.edu> wrote:
> 
> I think I've found that the latest release of qscintilla-2.10.7 doesn't work 
> (well) with latest sip/PyQt and private sip modules.  In particular, it 
> doesn't see to use the private one(s) at all by default, so applications 
> that try to use both PyQt and qscintilla, end up with runtime errors like:
> $ python3
> 
> > > > import PyQt4.QtCore
> > > > import PyQt4.Qsci
> Traceback (most recent call last):
> File "<stdin>", line 1, in <module>
> ValueError: PyCapsule_GetPointer called with incorrect name
> 
> I'm running into this problem quite a bit trying to integrate these latest 
> changes related to private sip modules in fedora packaging.  I'm having to 
> patch things to explicitly call
> sip -n PyQt4.sip ...
> or 
> sip -n PyQt5.sip ...
> (or use a /usr/bin/sip-pyqt4 or /usr/bin/sip-pyqt5 wrapper which does the 
> same thing).  Is this correct or am I missing something?

It will be fixed in the next release. Things are a bit delayed at the moment because \
I'm waiting for the release of Qt v5.11.2. For my purposes Qt v5.11 is unusable \
because of macOS regressions - which (I'm told) are fixed in v5.11.2.

Maybe wait for the moment?

Phil
_______________________________________________
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]