| 2010-10-20 11:27:58 |
Erkan Ozgur Yilmaz |
description |
For several reasons, the code examples in the documentation are cumbersome
- First of all, it doesn't show the import statement, which, I presume, is "from mocker import *", and this is something a good Python developer avoids all the time and makes the example unfamiliar for that particular developer.
- Uses of the word "mocker" as a variable holding a mock object confuses the readers mind because the word "mocker" is also the name of the package and without seeing the import statement at the beginning of the code example that forces you to guess and remember that the whole package is imported to the module namespace. |
For several reasons, the code examples in the documentation are cumbersome:
- First of all, it doesn't show the import statement, which, I presume, is "from mocker import *", and this is something a good Python developer avoids all the time and makes the example unfamiliar for that particular developer.
- Uses of the word "mocker" as a variable holding a mock object confuses the readers mind because the word "mocker" is also the name of the package and without seeing the import statement at the beginning of the code example that forces you to guess and remember that the whole package is imported to the module namespace.
|
|
