-
Notifications
You must be signed in to change notification settings - Fork 54
Use threading.Lock instead of QMutex to workaround QMutexLocker bug in PyQt6 #151
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use threading.Lock instead of QMutex to workaround QMutexLocker bug in PyQt6 #151
Conversation
|
Looks good to me. There doesn't seem to be any reason to use |
|
Unsurprisingly – now that we have @danielrh's root cause analysis showing that this is a bug in It would be good to cut a release with this as a matter of urgency, as this greatly improves the stability on Windows. (I'm not sure whether it was the recent switch to Windows 11 in the deployment here or upgrading the PyQt/Qt versions, but the current state is almost unusably unstable for our applications.) |
|
@hosaka: In case reviewing the state of master regarding a new release takes more bandwidth than you have to spare right now, could we potentially just backport this to 0.27.1 and release it as a follow-up 0.27.2? (Given that I had a close look into the threading model in #87, I'm confident in saying that this is at least as correct as the previous implementation that hits the PyQt bug.) |
|
Hi, thanks for the PR. Can we get a rebase on top of master to resolve the conflicts? And yeah it's about time we make a new release. |
…t and try to attempt isolation of CabbageDevelopment#128
b497a15 to
ed4fc1f
Compare
|
Sorry for the delay @hosaka : here's the rebase. I didn't notice any conflicts during the rebase? Are you sure you have github set to |
|
Thanks, I could swear GitHub showed me a "cannot automatically rebase" message... |
Coverage reportClick to see where and how coverage changed
This report was generated by python-coverage-comment-action |
||||||||||||||||||||||||
This solves #128