[Python-checkins] r83019 - sandbox/trunk/errnopep/pepXXXX.txt

[antoine.pitrou]

Author: antoine.pitrou
Date: Wed Jul 21 14:45:11 2010
New Revision: 83019

Log:
A couple of changes



Modified:
   sandbox/trunk/errnopep/pepXXXX.txt

Modified: sandbox/trunk/errnopep/pepXXXX.txt
==============================================================================
--- sandbox/trunk/errnopep/pepXXXX.txt	(original)
+++ sandbox/trunk/errnopep/pepXXXX.txt	Wed Jul 21 14:45:11 2010
@@ -62,10 +62,10 @@
 
 As for WindowsError, it seems to be a pointless distinction.  First, it
 only exists on Windows systems, which requires tedious compatibility code
-in cross-platform applications.  Second, since it inherits from OSError
-and is raised for similar errors as OSError is raised for on other systems.
-Third, the user wanting low-level access to exception specifics has to
-use the ``errno`` or ``winerror`` attribute anyway.
+in cross-platform applications.  Second, it inherits from OSError and
+is raised for similar errors as OSError is raised for on other systems.
+Third, the user wanting access to low-level exception specifics has to
+examine the ``errno`` or ``winerror`` attribute anyway.
 
 
 Lack of fine-grained exceptions
@@ -251,7 +251,7 @@
 
 * it introduces new syntax, which is perceived by the author to be a heavier
   change compared to reworking the exception hierarchy
-* it doesn't diminish typing effort significantly
+* it doesn't decrease typing effort significantly
 * it doesn't relieve the programmer from the burden of having to remember
   errno mnemonics
 
@@ -287,8 +287,12 @@
 
 * ``EINTR``: interrupted function call
 
+* ``EISDIR``: is a directory
+
 * ``ENOTDIR``: not a directory
 
+* ``ENOENT``: no such file or directory
+
 * ``EOPNOTSUPP``: operation not supported on socket
   (possible confusion with the existing io.UnsupportedOperation)
 
@@ -308,7 +312,7 @@
 
 * ``ENODEV``: no such device
 
-* ``ENOENT``: no such file or directory
+* ``ENOENT``: no such file or directory (when trying to open())
 
 * ``ETIMEDOUT``: connection timed out
 
@@ -316,7 +320,7 @@
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 All these errors may also be associated with a plain IOError, for example
-when calling read() on a socket file descriptor.
+when calling read() on a socket's file descriptor.
 
 * ``EAGAIN``: resource temporarily unavailable (during a non-blocking socket
               call except connect())