You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Similarly, the problem can be avoided by turning %autocall completely off. We still need to investigate whether we can fine-tune %autocall to still work while producing less spurious getattr calls.
Honestly, I don't think this is fixable while having autocall active. Autocall needs to inspect the objects fairly aggressively and I don't think we can make it work without triggering getattrs. The answer is simply: if your objects have so many side effects that you can't call getattr on them more than once, disable autocall altogether.
Original Launchpad bug 297501: https://bugs.launchpad.net/ipython/+bug/297501
Reported by: fdo.perez (Fernando Perez).
Reported on the ipython-user list:
I am experiencing some unusual behavior only when I am directly
working in the ipython shell. The problem involves the get method for
a property.
If you stick all this in a file and do 'run test.py', the problem does
not occur. Also, notice that it does not occur in the "print a.x"
statement.
The text was updated successfully, but these errors were encountered: