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

List:       pykde
Subject:    Re: [PyQt] PYQT_CONFIGURATION["sip_flags"]
From:       Phil Thompson <phil () riverbankcomputing ! com>
Date:       2018-08-27 15:01:16
Message-ID: A3E2CB25-3E1F-4D02-BC89-723D28DD800D () riverbankcomputing ! com
[Download RAW message or body]

On 27 Aug 2018, at 3:38 pm, Rex Dieter <rdieter@math.unl.edu> wrote:
> 
> As suggested, I've started researching how to make various sip/PyQt 
> consumers respect PYQT_CONFIGURATION, in particular, 
> PYQT_CONFIGURATION["sip_flags"].
> 
> This was useful,
> $ python3
> ...
>>>> from PyQt5.Qt import PYQT_CONFIGURATION;
>>>> print(PYQT_CONFIGURATION["sip_flags"])
> -n PyQt5.sip -t WS_X11 -t Qt_5_10_1
> 
> and the idea is that related python modules should pass those same arguments 
> to sip?  (or is just the -n PyQt5.sip piece enough?)

All of them.

> I wondered because kde's 
> https://phabricator.kde.org/D15091
> code review seems to be extracting and using only the -n ... part

They must be specifying the other flags elsewhere - not DRY.

> Next,
> 
> $ python3
> ...
>>>> from PyQt4.Qt import PYQT_CONFIGURATION
>>>> print(PYQT_CONFIGURATION["sip_flags"])
> -x VendorID -t WS_X11 -x PyQt_NoPrintRangeBug -t Qt_4_8_6
> 
> shouldn't PyQt4-4.12.2 be including '-n PyQt4.sip' in there?

Yes - that's a (very annoying) bug. It probably merits a v4.12.3.

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]