Pyqtdeploy plan for the end of qmake?

[Patrick Stinson]

Looping back here after having time to verify how all this works.

sip5 becoming a self-contained build system finally made it possible to develop a pyqt5 app continuing proprietary sip extensions using the qt.io and python.org installers.

Though I see conceptual inconsistencies between how in-app sip extensions are handled by sip-build in the dev phase and pyqtdeploy-sysroot/pyqtdeploy-build in release phase, I think that overall the ability to use a python virtual env in dev instead of building everything from source removes a major bottleneck for pyqt5 developers.

I just hope the concepts don’t all change again with sip6….

> On Sep 2, 2020, at 9:52 AM, Patrick Stinson <patrickkidd at gmail.com> wrote:
> 
> That is correct. Phil did say that earlier. I appreciate both of your patience as I soak this info up.
> 
> I will move additional questions to new threads.
> 
> -Patrick
> 
>> On Sep 2, 2020, at 3:04 AM, michael h <michaelkenth at gmail.com <mailto:michaelkenth at gmail.com>> wrote:
>> 
>> 
>> On Tue, Sep 1, 2020 at 8:18 PM Patrick Stinson <patrickkidd at gmail.com <mailto:patrickkidd at gmail.com>> wrote:
>> Indeed. I have been putting off understanding sip5 but I just went through it all. It took a while to understand from the docs, but nice work.
>> 
>> It looks like the correct way to get the .sip files installed for PyQt5 is to use sip-install or PyQt-Builder to install PyQt5 from source?
>> 
>> Not sure if I missed something in the thread about building from source, but if you install PyQt5 from the wheels on pypi it will include the sip files...in PyQt5/bindings iirc...
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.riverbankcomputing.com/pipermail/pyqt/attachments/20201009/b5e7ec77/attachment.htm>