➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: Reorganize unittest.mock docs into linear manner
Type: enhancement Stage: needs patch
Components: Documentation Versions: Python 3.4, Python 3.5
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: docs@python Nosy List: docs@python, ezio.melotti, michael.foord, py.user, rbcollins
Priority: normal Keywords:

Created on 2014-09-05 21:02 by py.user, last changed 2022-04-11 14:58 by admin.

Messages (1)
msg226456 - (view) Author: py.user (py.user) * Date: 2014-09-05 21:02 
Now, it's very inconvenient to learn this documentation. It's not compact (could be reduced in 2 or even 3 times). It repeats itself: many examples copy-pasted unchangeably. And it cites to terms that placed under those cites, so people should start at the bottom to anderstand what it's talking about on the top.

Remember Zen "If the implementation is hard to explain, it's a bad idea."

- Move the MagicMock description to the point between Mock and PropertyMock descriptions
- Remove "copy-paste" examples
- Rename print to print() and StringIO to io
- Split the Autospecing section to several chunks
History
Date User Action Args
2022-04-11 14:58:07adminsetgithub: 66540
2014-11-02 18:09:45pitrousetnosy: + rbcollins
2014-11-02 15:22:15ezio.melottisetnosy: + ezio.melotti

stage: needs patch
2014-09-05 21:43:50ned.deilysetnosy: + michael.foord

versions: + Python 3.5
2014-09-05 21:02:07py.usercreate