diff options
| author | Andrew Kuchling <amk@amk.ca> | 2014-04-16 01:11:36 (GMT) |
|---|---|---|
| committer | Andrew Kuchling <amk@amk.ca> | 2014-04-16 01:11:36 (GMT) |
| commit | 764662020ba496164bf8dcb96d93c519f0968405 (patch) | |
| tree | 84f53d4d960fa87fe24dbcd923a16f5bc3e7b1b7 | |
| parent | fc1020d39603418b1c10a5a68b4a195133b4b955 (diff) | |
| download | cpython-764662020ba496164bf8dcb96d93c519f0968405.zip cpython-764662020ba496164bf8dcb96d93c519f0968405.tar.gz cpython-764662020ba496164bf8dcb96d93c519f0968405.tar.bz2 | |
#15840: make docs consistent by saying operations on closed files raise ValueError.
Patch by Caelyn McAulay.
Neither Caelyn nor I could find any cases in 2.7 or 3.4/5 where an
operation on a closed stream raised IOError; generally the C
implementations have a macro to check for the stream being closed, and
these macros all raised ValueError. If we find any, a new bug should
be opened.
| -rw-r--r-- | Modules/_io/iobase.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Modules/_io/iobase.c b/Modules/_io/iobase.c index e372990..ef06b43 100644 --- a/Modules/_io/iobase.c +++ b/Modules/_io/iobase.c @@ -42,8 +42,8 @@ PyDoc_STRVAR(iobase_doc, "bytes. bytearrays are accepted too, and in some cases (such as\n" "readinto) needed. Text I/O classes work with str data.\n" "\n" - "Note that calling any method (even inquiries) on a closed stream is\n" - "undefined. Implementations may raise IOError in this case.\n" + "Note that calling any method (except additional calls to close(),\n" + "which are ignored) on a closed stream should raise a ValueError.\n" "\n" "IOBase (and its subclasses) support the iterator protocol, meaning\n" "that an IOBase object can be iterated over yielding the lines in a\n" |