Nuitka: PySide6.1.0 and PySide6.1.1 still doesn't work, PySide 6.1.2 will be needed
- Nuitka version, full Python version and Platform (Windows, OSX, Linux …)
0.6.15rc6
Python: 3.9.1 (tags/v3.9.1:1e5d33e, Dec 7 2020, 17:08:21) [MSC v.1927 64 bit (AMD64)]
Executable: D:\Programme\Python\Kanzlei\Contacts4Snom\venv\Scripts\python.exe
OS: Windows
Arch: x86_64
-
How did you install Nuitka and Python
pip, virtualenc
-
Also supply a Short, Self Contained, Correct, Example
Not shure where it comes from
I wroten an application (with pyside6 6.1.0) that uses multiple event-slots:
self.actionBeenden.triggered.connect(self.MainWindow.close)
self.pushButton.clicked.connect(self.KonfigurationSpeichern)
self.comboBox.currentIndexChanged.connect(self.GeanderterDienst)
self.actionLizenz.triggered.connect(self.Lizenzdialog.show)
self.Lizenz_Deaktivieren.clicked.connect(self.deactivateLicense)
self.pushButton_3.clicked.connect(self.GoogleLogin)
self.pushButton_4.clicked.connect(self.GoogleLogin)
self.pushButton_2.clicked.connect(self.KontakteErzeugen)
self.statusBar.messageChanged.connect(self.KontaktErzeugenStatus)
self.pushButton_5.clicked.connect(self.Microsoft365Login)
self.lineEdit.textChanged.connect(self.RequierementCheck)
There seem to multiple issues with them:
- they seem to call random functions:
my setup codes calls a function
KonfigurationLesen(), which doesn’t callKonfigurationSpeichern(), but in compiled mode it does? - the function
RequierementCheckcallsself.KonfigurationSpeichern(silent=True), but the paramter silent=True will not be handed over, instead the default parameter silent=false is used
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 24 (23 by maintainers)
@ctismer I tried to bisect the other day, and I am suprised, but this is actually not working with my patch applied. My mental sanity is taking a severe hit, because I backported the exact same code for PySide2 and there the issue doesn’t arise. So no regression on your side. I will track this down on current “dev” and open a PySide issue once I have a patch. It seems something there only worked by accident or whatever, but I will only really know once I find it.