Ссылка
click to show
click to show
info : for Qt 5.15 there is some more things to install if you want to use pytest-qt : https://github.com/pytest-dev/pytest-qt/commit/2c2745c82b437917236f0705ecfdd382c4cdccfb#diff-4f31c1e2c9e43e4d6edbcd36ed58f8b8
12 June 2020
Hi there. I faced with strange behavior. I always thought, that signal/slot system works as triggered slot code wont run until emitter code ends and flow goes back to qt loop. But, right now I see, that signal.emit() blocks, until connected slot done. Pure python signal and slot to be exact. Is it normal?
Here is tiny example which leads to python recursion limit:
from PySide2.QtCore import QObject, Signal, Slot
from PySide2.QtWidgets import QApplication
class T(QObject):
signal = Signal()
def __init__(self):
super().__init__()
self.signal.connect(self.slot)
@Slot()
def slot(self):
print("enter action")
self.signal.emit()
print("exit action")
app = QApplication()
t = T()
t.slot()
app.exec_()
Ссылка
click to show
click to show
Ah, okay, this is my bad... I did not know about https://doc.qt.io/qt-5/qt.html#ConnectionType-enum
Nikita MelentevAh, okay, this is my bad... I did not know about https://doc.qt.io/qt-5/qt.html#ConnectionType-enum
QTimer.singleShot(0, self.signal.emit) where you emit the signal might be a more explicit solution