New submission from Pawel :
When method of mocked object is called multiple times with mutable object as
parameter and attribute of this object has been updated between calls,
mock_calls is only aware of the last value. I think it unexpected behaviour,
that mock doesn't track value ch
Pawel added the comment:
Ok, fair enough. Thank You for explanation. I was just surprised with this
behaviour.
On the other hand, I don't like mutable objects and I'm trying to avoid them.
--
___
Python tracker
<https://bugs.python.o
New submission from Pawel :
In this question:
https://docs.python.org/2.7/faq/programming.html#how-do-i-convert-a-number-to-a-string
There is a statement:
"{:.3f}".format(1/3) yields '0.333'
While
In [2]: "{:.3f}".format(1/3)
Out[2]: '0.000'
In [3
New submission from Pawel Prokop <[EMAIL PROTECTED]>:
I've needed to measure each unit test running time
to measure the performance changing of each functionality
that every test case tests.
Latest version of pyunit has only displayed summary running time of the
suite, so I've i
Pawel Prokop added the comment:
I agree with Ezio,
this feature should have an option to enable/disable.
Anyway, I use it in different way.
Since 2008, I've used this feature for performance comparision, whether some
implementation changes in application code did not slow down applic
Pawel Prokop added the comment:
Repack of unittest was good idea. It is a patch against trunk, one test
case is provided and documentation update.
--
Added file: http://bugs.python.org/file15332/unittest_runTime.patch
___
Python tracker
<h
Pawel Prokop added the comment:
I think that a delay time of calling a decorator is not important, because this
should be constant in each test execution, so no matter.
I shall be able to provide a patch in few days.
Thanks
--
___
Python tracker
