Re:Hello Qt for Python
by Drdrdrq on Saturday May 05, 2018 @04:52PM
(#17003739)
This just means that wrapper around C(++) code doesn't handle resources correctly. As you said, once inside Python you shouldn't care about object collection process. Nothing should lead to segfaults, in worst case you should get an exception about missing parent ref.
[ Parent
| on HN ]
more exactly “underlying C/C++ object has been deleted" error.
Re:Hello Qt for Python
by JasonFruit on Sunday May 06, 2018 @08:48AM
(#17006219)
In my experience, those errors are easy to resolve: just assign the new object to something, so it isn't immediately deleted. A little awkward, maybe, and it shouldn't happen, but if that's the worst quirk of PyQT/PySide, I can deal.
Those errors are always related with a bad implementation where there is something holding a reference to the qt python object represented by the bidding therefore keeping it alive even when their c++ instance has been already deleted. The solution is to go back to the drawing board and improve the implementation :)