Hi All,
I bumped into this using Michael Foord's Mock library.
It feels like a bug to me, but thought I'd ask here before logging one
in the tracker in case people know that we won't be able to fix it:
On 05/11/2012 13:43, Michael Foord wrote:
class Foo(object):
... def __setattr__(s, k, v):
... print k
...
f = Foo()
f.g = f.x = 3
g
x
Hmm, that's definitely counter-intuitive. Worth raising on python-dev?
Well, I guess "it's always been that way", so changing it would be backwards
incompatible. Feel free to raise it though. :-)
Here's the actual problem I had:
mock = Mock()
inst = mock.Popen.return_value = mock.Popen_instance = Mock(spec=Popen)
Here the *return_value* is set first. So when mock.Popen_instance is assigned
it already has a parent! (Setting a mock as the return value of another mock
also establishes the child / parent relationship.)
This is why calls to the instance are then not recorded in "method_calls".
cheers,
Chris
--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
