Reorganize unittest.mock docs into linear manner

[py-user]

BPO	22344
Nosy	@rbtcollins, @ezio-melotti, @voidspace, @py-user

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = None
created_at = <Date 2014-09-05.21:02:07.134>
labels = ['type-feature', 'docs']
title = 'Reorganize unittest.mock docs into linear manner'
updated_at = <Date 2014-11-02.18:09:45.183>
user = 'https://github.com/py-user'

bugs.python.org fields:

activity = <Date 2014-11-02.18:09:45.183>
actor = 'pitrou'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2014-09-05.21:02:07.134>
creator = 'py.user'
dependencies = []
files = []
hgrepos = []
issue_num = 22344
keywords = []
message_count = 1.0
messages = ['226456']
nosy_count = 5.0
nosy_names = ['rbcollins', 'ezio.melotti', 'michael.foord', 'docs@python', 'py.user']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue22344'
versions = ['Python 3.4', 'Python 3.5']

[py-user]

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