[issue21611] int() docstring - unclear what number is

2018-03-16 Thread Dmitry Andreychuk
Dmitry Andreychuk added the comment: I created this issue almost 4 years ago. Looking at it now, I think that I was asking too much of that docstring. I believe it's current version quite sufficient. I would close the issue, but I'm not sure if it's up

[issue21478] mock calls don't propagate to parent (autospec)

2014-05-12 Thread Dmitry Andreychuk
New submission from Dmitry Andreychuk: Calls to autospecced mock functions are not recorded to mock_calls list of parent mock. This only happens if autospec is used and the original object is a function. Example: import unittest.mock as mock def foo(): pass parent = mock.Mock

[issue21611] int() docstring - unclear what number is

2014-05-30 Thread Dmitry Andreychuk
New submission from Dmitry Andreychuk: https://docs.python.org/3.4/library/functions.html?highlight=int#int The docstring for int() function has these sentences: "If x is a number, return x.__int__()." "If x is not a number or if base is given..." Unfortunately the docstr

[issue21611] int() docstring - unclear what number is

2014-06-01 Thread Dmitry Andreychuk
Dmitry Andreychuk added the comment: Now I see that my message may look like a suggestion to add an encyclopedic definition of number there. Sorry. Actually I was talking about requirements for user-defined types to make them work with int(). Something like: "If x has __int__() method r

[issue23661] Setting a exception side_effect on a mock from create_autospec does not work

2015-11-18 Thread Dmitry Andreychuk
Dmitry Andreychuk added the comment: python 3.4.3 is also affected. Is it possible to fix this in branch 3.4? -- nosy: +and versions: +Python 3.4 ___ Python tracker <http://bugs.python.org/issue23