`copy` module covers very important aspect of Python programming. However its documentation doesn't provide any intro or overview of this problem starting right from details. When people meet `copy` construction in the code - the refer to module documentation and its doesn't completely answer two basic questions they have:

1. why copy module is needed (i.e. what's the problem with var assignment)
2. when and where it should be used

The intro paragraph currently (3.2a) consists of
"This module provides generic (shallow and deep) copying operations."

This could be expanded to '''
Assignment statements create bindings between a target and an object. They never duplicate or copy an existing object. For collections that are mutable or contain mutable items, a copy is sometimes needed so one can change one copy without changing the other. Sequences can be shallow copied by slicing the entire sequence(s[:]). (See below for the meaning of 'shallow'.) Some objects can be shallow copied with their class constructors (tuple, list, set, dict). This module provides generic shallow *and* deep copying operations. The latter is not otherwise available in an single operation or call.'''

Shorter and better version.

Assignment statements create bindings between a target and an object. They never duplicate or copy an existing object. For collections that are mutable or contain mutable items, a copy is sometimes needed so one can change one copy without changing the other. This module provides generic shallow and deep copy operations (explained below). Shallow copies can also be obtained by whole sequence slicing (s[:]) and some class constructors (tuple, list, set, dict).

I am +0 on this change. The existing introduction is fine and the
discussion where shallow and deep copy is discussed is more important.

It is okay to assume that the reader is aware of the assignment
operation nature, i.e. it does not create a copy and you need this
module.  

The doc change suggested by Terry could be helpful in the tutorial
where a copy module is mentioned.

> The doc change suggested by Terry could be helpful in the tutorial
> where a copy module is mentioned.

Can you post a link to this tutorial here?

> Can you post a link to this tutorial here?

Section 9.1 and 9.2 of the docs.python.org/tutorial
It may not be as explicit as you might want it to be, but it does sets
up background that assignments do not copy the object.

New changeset 0e050b38e92b by Senthil Kumaran in branch '2.7':
Issue #9021: Add an introduction to the copy module. Doc changes suggested by Terry Reedy.
http://hg.python.org/cpython/rev/0e050b38e92b

New changeset a352e24b9907 by Senthil Kumaran in branch '3.2':
Issue #9021 - Introduce copy module better. Doc changes suggested by Terry
http://hg.python.org/cpython/rev/a352e24b9907

New changeset bf6f306ad5cf by Senthil Kumaran in branch 'default':
merge from 3.2
http://hg.python.org/cpython/rev/bf6f306ad5cf

Added suggested changes to the documentation. Thanks.

Perfectionist in me says that now copy.copy theory should be diluted with examples for those who can't grasp the concept of "binding of variables", but the patch perfectly covers the original user story. Thanks.