Any Qt + Python devs out there with any experience on calling deleteLater() from the Python side?
I have some costly dialogs I want cleared on close, and so far I've been running deleteLater() in the closeEvent, which is clearly a little risky. I do get the very rare segfault especially if I close one particular dialog which has a QTimer singleShot call. If the deleteLater() is called when it is running, I get a RunTImeError.
Another update on "memory leaking" when combining Qt and Python. It seems using lambda functions as slots for signals on dialogs block the widgets from being deleted by Qt.
I just rewrote the code and added dedicated slots for the four buttons sharing the same slot via lambdas, so no big deal, but maybe just disconnecting the signals on close would have been enough.
@arnfinnp Well, yes. It is definitely a reflection of his attitude. I mena, he wasn't the only writer, so it is at least somewhat more nuanced I guess.
The show is definitely a mixed basket. I do like Jason Alexander, Julia Louis-Dreyfus, Jerry Stiller, Estelle Harris and some of the other very funny actors. They're what make the show funny. Especially Jason Alexander.
FTR. "AI" isn't just LLMs. Besides generative "AI" we also have iterative "AI" and classic Machine Learning. The latter two are well established and useful tools, IMHO. Throwing them all under the generic "AI" umbrella term doesn't do them justice.
Ok, so I got the Facebook email today about the sneaky change in their TOS to steal more user data. This time for "AI".
That's it. I deleted my account. I wasn't using it anyway, but I kept it to keep Messenger working. I created a new Messenger account instead for the handful of cases where I still need it.
I had not yet accepted the changed TOS from last year, and had to "consent" to those outrageous terms too just to get to the delete button. Clearly illegal.