As explained on mailing list[1] check those types of problems would slow down
object creation and turn impossible some things like method duck punching, so
marking as WONTFIX.

[1] http://lists.pyside.org/pipermail/pyside/2011-June/002582.html

Regards

release 1.0.4

This issue is still not resolved in 1.0.4

And I still suggest:

"Try to resolve the method. If that is not possible (AttributeError)
print warning and return dummy object to C++ interface."

This should only have a negligible overhead for normal method dispatching but
would make it much easier to track down such an error.

Christian, read the comment #1

Regards.

I suggest to adapt the existing code to something like that (Python like pseudo
code):


try:
    func = getattribute(obj, virtual_method_name)
except AttributeError:
    print 'Cannot find virtual method ... '
else:
    res = func(*args)
    if isinstance(res, expected_return_value):
        return res.cobject()
    else:
        print 'Invalid return value, got ... expected ... '
return <dummy cobject>



regarding comment #1
> As explained on mailing list check 
> those types of problems would slow down object creation 

I am not suggesting and I have never suggested to do any checks at object
creation time. You are right that would be a huge slowdown.

> and turn impossible some things like method duck punching

Why should method duck punching be broken?

(In reply to comment #5)
> I suggest to adapt the existing code to something like that (Python like pseudo
> code):
> 
> 
> try:
>     func = getattribute(obj, virtual_method_name)
> except AttributeError:
>     print 'Cannot find virtual method ... '
> else:
>     res = func(*args)
>     if isinstance(res, expected_return_value):
>         return res.cobject()
>     else:
>         print 'Invalid return value, got ... expected ... '
> return <dummy cobject>
> 
> 
> 

The PySide implementation already do something similar to this, but the problem
here is that, the error occurred during the c++ call, at this point PySide set
the python error with the necessary values, this error will be raised when the
python interpret returns. But the this never happen because all code python has
already executed.

This is how python works we can not change that. You can have more information
about that on python documentation:
http://docs.python.org/c-api/exceptions.html


Feel free to suggest some different solutions.

Thanks

Since we did not receive any reply during the release window, I will mark this
bug as WONTFIX. But feel free to re open if necessary.

Release PySide 1.0.6