Qt for Python (PySide/Shiboken) — messages on 7 March 2025

7 March 2025

monkey.D.Dragontext not yet in the index

I assume the bundling is not the problem here? LIke the UI is laggy when run with a standard pythonw.exe?

What you can do is having a separate process doing the heavy lifting and the main UI process talking to it.

In Python all threads, be it vanilla threading or QThread will run in the one main process sharing memory and resources.

08:23

(of course any tipps on making stuff more efficient are also valid!! might well be you identify and fix one or two bottleneck things and don't need to worry about lag anymore at all)

08:27

Valery

monkey.D.Dragontext not yet in the index

Another way to try is Nuitka. There is possibility that after translation to C and compiling it, application would be faster but not granted

08:35

Thomas

BTW: Whats the status with PyPy? That should also be faster in many cases. The packaging ecosystem is worse, though. But the last PySide6 wheels for PyPy are for 6.5.2

08:44

Christian Tismer-Sperling

Ссылка
click to show

Nuitka would not affect threading per se, it would make some Python code a little faster. We started avoiding the GIL last year, with not much response. This is now being taken up again. https://peps.python.org/pep-0703/

08:46

Thomas

Afaik that is not yet supported by PySide6. Once that works, it may be a nice alternative

08:49

Christian Tismer-Sperling

@luziferius yes, the absolute winner would be PyPy and GIL removal. But there are no current plans in that direction because of too little resources.

08:50

alexis jeandet

on my quest to not write XML files to generate bindings, I rediscovered this https://bugreports.qt.io/browse/QTBUG-80687, is there any progress on this front?

10:07

A snapshot of an open public feed from the search index ChatCrawler — “Google for public Telegram”; refreshed as the venue is crawled. Times are UTC.