Cristián 🥑no free threading, but everything else does :)
Wasn't that exactly the point to switch to 3.14?
Ссылка
click to show
click to show
why would be one feature the reason to update? there are so many changes!
https://docs.python.org/3/whatsnew/3.14.html
Keith KyzivatIf free-threading was the only reason to upgrade, there wouldn't be a separate non-free-threaded build.
This is early-days for GIL-free python threading.
Hi, "Qt Developer" this developer pyside6? Or what
I'm developing an application that requires heavy background tasks, using QThread. But also, after reading, Slot options are offered for transferring information to streams. I also tried using just a global instance of my settings class, and I successfully change attribute in classes at any stage as well as reading them. What's the point of using Slot then? or is it just to maintain the code structure of c/c++ languages? (I know that global variables are bad, but I think it's very good to make global settings so that don't always transfer between threads all the time)
after updating to 6.10.1, our CI is consistently hitting a segmentation fault with multiple tests related to Qt, for macOS, Linux and Windows, and Python 3.12
<https://github.com/randovania/randovania/actions/runs/19570721087/job/56043345290?pr=8801#step:9:32>
is this something known about?
Maybe not a true Python question but closely related to the bottle necks in QML. I have experienced before that QML has some limitions when doing processing heavy image and video stuff. Together with the original single thread nature of Python I did many workarounds before.
Now exists the (wayland) compositor. Considering I control all the hardware myself. Would there be a benefit of running independent proces-es on top of the compositor. Or should running the entire thing in a single application be 'better'.
Practically I typically benchmark the behavior of the GUI using a marquee style element where I expect that that marquee is completely stable and stutter free. I have noticed before that running this is a dedicated application is much more stable than being part of a bigger application.
ZI'm developing an application that requires heavy background tasks, using QThread. But also, after reading, Slot options are offered for transferring information to streams. I also tried using just a global instance of my settings class, and I successfully change attribute in classes at any stage as
In Python, if you have a global settings class and you're using multiple threads (main thread plus one QThread would count), that both access the settings, and at least one of them is altering the settings (as in, it's not just constant settings that are set once before the threads start), in *Python* with the GIL involved, I believe you don't really need to worry about corruption (reading a settings value while it is in the middle of being updated), because the GIL will gate that. However, if threaded C++ code is involved, the GIL is out of the picture in that thread, and your python code could be reading a value that is in the middle of being updated.
This is where Signals and slots are useful across QThread boundaries, as the slot call is actually done on the thread that owns that slot (Every QObject has a thread it belongs to, and the slot is part of a QObject), so, there's no concern of corruption given that only that one thread manages the data.
How it works is that an event for the signal gets created on the receiving object's QThread's event queue, and when the thread is servicing it's event queue and that event comes up, the event queue processing calls the slot.
The queue processing itself is guarded by mutexes behind the scenes.
Replymessage unavailable
Running pip debug --verbose says (in parts)
Compatible tags: 42
cp312-cp312-linux_aarch64
cp312-abi3-linux_aarch64
cp312-none-linux_aarch64
cp311-abi3-linux_aarch64
cp310-abi3-linux_aarch64
[...]
So the official wheels targeting manylinux_aarch64 are incompatible. This looks like you have to compile from source, either on the device or by cross compiling
cool smilepyside6 will report an error when running the following code on Android, and the QtWebView.abi3.so cannot be found
from PySide6.QtWebView import QtWebView
Wow, I'm surprised pyside6 works on Android at all!