[Development] Technical vision for Qt for Python
jhihn at gmx.com
Mon Aug 19 15:52:14 CEST 2019
I tried PySide 2, and was extremely disappointed that not all the classes are supported. What's worse it PyQt supports the classes that are not supported. Having that kind of errata is devastating to the confidence in a project. Qt6/PySide6 must have parity from day 1.
Next, the biggest flaw is lack of Python 3 native event loop integration. A lot of people have codebases Python 3 event loops now, PySide should be seamless from day 1.
Jupiter concerns me. I'm wondering how well we can get Qt to integrate with Jupiter notebooks? Can we get interactive Qt in the notebook? (WASM?)
Finally, I've used PyQt off and on since Qt 3.3 days. I really like Python as a language to use Qt in a rapid prototype development way, but the limitations stated above prevent it from being my default environment.
1. Since Qt lagged many years in getting an ECMA Script 7 implementation, chasing this evolving standard might not be the best.
2. Why maintain V4?
> Sent: Monday, August 19, 2019 at 8:39 AM
> From: "Cristián Maureira-Fredes" <Cristian.Maureira-Fredes at qt.io>
> To: "development at qt-project.org" <development at qt-project.org>
> Subject: [Development] Technical vision for Qt for Python
> It will be really nice to know what do you think,
> because at the moment we have been mostly community driven,
> and many aspects from the C++ expertise on this mailing list
> will help us improving Qt for Python.
More information about the Development