iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Typo fixes by Éric Araujo.

This commit is contained in:
Antoine Pitrou 2010-07-26 22:20:52 +00:00
parent 73f8b2df7c
commit c7a8f5a164
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
pep-3151.txt
View File

@ -40,7 +40,7 @@ Confusing set of OS-related exceptions
--------------------------------------
OS-related (or system call-related) exceptions are currently a diversity
of classes, arranged in the following subhierarchies::
of classes, arranged in the following sub-hierarchies::
+-- EnvironmentError
+-- IOError
@ -95,7 +95,7 @@ exception specifics has to examine the ``errno`` or ``winerror`` attribute
anyway.
.. note::
`Appendix B`_ surveys the use of the various exception types accross
`Appendix B`_ surveys the use of the various exception types across
the interpreter and the standard library.
@ -178,7 +178,7 @@ and define as follows:
* *useful compatibility* doesn't alter the behaviour of *careful*
exception-catching code. Given the following kind of snippet, the same
errors should be silenced or reraised, regardless of whether this PEP
errors should be silenced or re-raised, regardless of whether this PEP
has been implemented or not::
try:
@ -213,9 +213,9 @@ The following changes are proposed:
Each of these changes doesn't preserve exact compatibility, but it does
preserve *useful compatibility* (see "compatibility" section above).
Each of these changes can be accepted or refused invididually, but of course
Each of these changes can be accepted or refused individually, but of course
it is considered that the greatest impact can be achieved if this first step
is accepted in full. In this case, the IO exception subhierarchy would
is accepted in full. In this case, the IO exception sub-hierarchy would
become::
+-- IOError (replacing OSError, WindowsError, EnvironmentError, etc.)
@ -667,7 +667,7 @@ object would block.
mmap
''''
Undex Unix, raises its own ``mmap.error`` (inheriting from EnvironmentError)
Under Unix, raises its own ``mmap.error`` (inheriting from EnvironmentError)
throughout::
>>> mmap.mmap(123, 10)
@ -711,7 +711,7 @@ os / posix
''''''''''
The ``os`` (or ``posix``) module raises OSError throughout, except under
Windows where WindosError can be raised instead.
Windows where WindowsError can be raised instead.
ossaudiodev
'''''''''''