Clarify statement at Barry's request
This commit is contained in:
parent
500d47d62b
commit
fe1e5f6de7
|
@ -193,10 +193,14 @@ Then we can define *useful compatibility* as follows:
|
|||
* useful compatibility doesn't make exception catching any narrower, but
|
||||
it can be broader for *careless* exception-catching code. Given the following
|
||||
kind of snippet, all exceptions caught before this PEP will also be
|
||||
caught after this PEP, but the reverse may be false::
|
||||
caught after this PEP, but the reverse may be false (because the coalescing
|
||||
of ``OSError``, ``IOError`` and others means the ``except`` clause throws
|
||||
a slightly broader net)::
|
||||
|
||||
try:
|
||||
...
|
||||
os.remove(filename)
|
||||
...
|
||||
except OSError:
|
||||
pass
|
||||
|
||||
|
|
Loading…
Reference in New Issue