http://docs.python.org/dev/howto/doanddont.html use twice in example the
"opne" function, which should be written as "open". From google it seems
that also 3.x is affected (but not really checked)

Here's a patch for trunk.

That "typo" is intentional, it's also written in the comment:
try:
    foo = opne("file") # misspelled "open"
except:
    sys.exit("could not open file!")

This example shows how a bare except will catch the NameError caused by
'opne' and return the wrong error message, whereas "except IOError" will
only catch IOErrors and show the NameError.

That'll teach me to pay more attention before submitting a patch. 
Thanks Ezio!

Actually, what's the second example trying to show:
try:
   foo = opne("file") # will be changed to "open" as soon as we run it
except IOError:
   sys.exit("could not open file")

I'm not sure what that comment really means?

If we use the bare "except:" the message "could not open file!" is shown
and we would waste time trying to figure out why it can't be opened.

Instead, if we use "except IOError:", the first time we run the program
the error "NameError: name 'opne' is not defined" is raised, telling us
what's wrong. Once we know it, we can change 'opne' to 'open' and solve
the problem.

Indeed it could be clearer.