ext Marcelo Lira wrote:
How about any other methods in other Qt classes? I'm just worried it might
become
confusing if only some PySide class methods throw exceptions but not all.
I agree. The modifications can start in the I/O operations and continue to other
similar cases where it makes sense, but keep the later cases in different PSEPs,
perhaps grouped by topic.
I wonder how this would work out, schedule-wise. After the first stable
release of the new API, we can't keep on making gradual, incompatible
changes to it, so all of the error handling changes would need to be
implemented by that time.
So, we'd have to throw exceptions in all the methods that natively
report errors by return values. (I believe having only some classes
throw exceptions would be the worst-case situation from the Python
coder's point of view.)
How much of the process could be automated? At least the return values
would need to be checked on method-by-method basis, which sounds like a
humongous task, especially if some meaningful exceptions would be thrown.
Furthermore, I'm more and more worried that we'd be throwing too much of
Qt compatibility out of the door--porting to and from C++ would become
quite non-trivial, and PySide learning curve would only become steeper,
not gentler as the differences from Qt increase.
ma.
_______________________________________________
PySide mailing list
[email protected]
http://lists.openbossa.org/listinfo/pyside
