Comments on: Mocker 0.9 http://blog.labix.org/2007/11/17/mocker-09 by Gustavo Niemeyer Mon, 16 Jan 2012 12:12:57 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Gustavo Niemeyer http://blog.labix.org/2007/11/17/mocker-09/comment-page-1#comment-21916 Gustavo Niemeyer Wed, 05 Dec 2007 16:47:58 +0000 http://blog.labix.org/2007/11/17/mocker-09/#comment-21916 Oops.. it was incorrect indeed. I've fixed that, and have also renamed all "mock" instances in the documentation to "obj", reducing a bit the volume of "mock" prefixes and thus the confusion. Thanks for reporting this. Oops.. it was incorrect indeed. I’ve fixed that, and have also renamed all “mock” instances in the documentation to “obj”, reducing a bit the volume of “mock” prefixes and thus the confusion.

Thanks for reporting this.

]]> By: Mike Pirnat http://blog.labix.org/2007/11/17/mocker-09/comment-page-1#comment-21915 Mike Pirnat Wed, 05 Dec 2007 16:05:05 +0000 http://blog.labix.org/2007/11/17/mocker-09/#comment-21915 I've been using PyMock a lot, and I'm very happy to see that Mocker addresses a lot of my complaints about PyMock, not the least of which is documentation---thanks for the clear examples in the tutorial! There appears to be an error in the first example in the tutorial, though. Instead of "mock.restore()" and "mock.verify()", I believe it should be "mocker.restore()" and "mocker.verify()" since the mock objects themselves seem to be upset about receiving unexpected expressions if you try to call these methods on them instead of on the Mocker instance. Cheers! I’ve been using PyMock a lot, and I’m very happy to see that Mocker addresses a lot of my complaints about PyMock, not the least of which is documentation—thanks for the clear examples in the tutorial!

There appears to be an error in the first example in the tutorial, though. Instead of “mock.restore()” and “mock.verify()”, I believe it should be “mocker.restore()” and “mocker.verify()” since the mock objects themselves seem to be upset about receiving unexpected expressions if you try to call these methods on them instead of on the Mocker instance.

Cheers!

]]> By: alex dante http://blog.labix.org/2007/11/17/mocker-09/comment-page-1#comment-20861 alex dante Fri, 23 Nov 2007 03:47:18 +0000 http://blog.labix.org/2007/11/17/mocker-09/#comment-20861 Awesome, thank you! Awesome, thank you!

]]> By: Gustavo Niemeyer http://blog.labix.org/2007/11/17/mocker-09/comment-page-1#comment-20818 Gustavo Niemeyer Thu, 22 Nov 2007 13:24:18 +0000 http://blog.labix.org/2007/11/17/mocker-09/#comment-20818 The problem here is that IPython performs some basic inspection in the mock object, which ends up recording an action. I'll release a new version of Mocker which fixes this problem. Thanks for reporting it. The problem here is that IPython performs some basic inspection in the mock object, which ends up recording an action. I’ll release a new version of Mocker which fixes this problem.

Thanks for reporting it.

]]> By: alex dante http://blog.labix.org/2007/11/17/mocker-09/comment-page-1#comment-20796 alex dante Thu, 22 Nov 2007 02:47:58 +0000 http://blog.labix.org/2007/11/17/mocker-09/#comment-20796 Sorry, the output lines got eaten, they're both displaying repr output that reads: "mocker.Mock object at 0xb78e058c" cheers Sorry, the output lines got eaten, they’re both displaying repr output that reads: “mocker.Mock object at 0xb78e058c”

cheers

]]> By: alex dante http://blog.labix.org/2007/11/17/mocker-09/comment-page-1#comment-20795 alex dante Thu, 22 Nov 2007 02:46:09 +0000 http://blog.labix.org/2007/11/17/mocker-09/#comment-20795 Hey there. Very impressed with mocker, it's great to work with, although I initially thought there was an issue with it due to it's behaviour under iPython: In [1]: from mocker import Mocker In [2]: mocker = Mocker() In [3]: mock = mocker.mock() In [4]: mock.test1() Out[4]: In [5]: mocker.result('test1') In [6]: mocker.replay() In [7]: mock.test1() Out[7]: This behaves correctly under the bare interpreter, although it also outputs the "<mocker.Mock object ..." line (is this correct? it's not shown in the docs...). Any ideas on how I can get mocker running properly under iPython? Thanks for an incredibly handy module! Hey there. Very impressed with mocker, it’s great to work with, although I initially thought there was an issue with it due to it’s behaviour under iPython:

In [1]: from mocker import Mocker
In [2]: mocker = Mocker()
In [3]: mock = mocker.mock()
In [4]: mock.test1()
Out[4]:
In [5]: mocker.result(‘test1′)
In [6]: mocker.replay()
In [7]: mock.test1()
Out[7]:

This behaves correctly under the bare interpreter, although it also outputs the “<mocker.Mock object …” line (is this correct? it’s not shown in the docs…). Any ideas on how I can get mocker running properly under iPython?

Thanks for an incredibly handy module!

]]>