Hi, 2011/6/15 Christian Brugger <[email protected]>: > in the Zen of Python "Errors should never pass silently." PySide could > improve in at least two cases: > > 1. When deriving a Qt class with virtual methods in Python and > forgetting to implement all virtual methods the constructor returns a > object containing a Null Pointer which will inevitably cause problems > later. This Problem is particularly hard to track down for multiple > inheritance where it seems absolutely possible to create a object with > partly initialized parent objects. In that case it is very hard to > find the error since the object seems to be fully functional in the > first place.
Wouldn't the additional checks slow down object creation? I'm not sure if it is possible to do the checks at subclassing time (after the "class" block has been parsed). There's also a misleading error message (something along the lines of "object already deleted") when you forget to call the superclass constructor, but I'm not sure if there is anything that we can do about this. > 2. Invalid return types often seems to be unchecked from the Python > side and sometimes lead to hard freezes. Can you create small, self-contained test cases (scripts) out of these (as you did in your mail) that one can run and experience the problems? When you got that, please file a bug at http://bugs.pyside.org/. Thanks, Thomas _______________________________________________ PySide mailing list [email protected] http://lists.pyside.org/listinfo/pyside
