summaryrefslogtreecommitdiffstats
path: root/Lib/test/test_optparse.py
diff options
context:
space:
mode:
authorAndrew Kuchling <amk@amk.ca>2014-04-15 20:07:52 (GMT)
committerAndrew Kuchling <amk@amk.ca>2014-04-15 20:07:52 (GMT)
commit68e85e583484d1fde2170ea768413eae818aa050 (patch)
tree20809e673e0d83dc574b7383592209a081667ca0 /Lib/test/test_optparse.py
parent49bf4ce563ce3273ef123efc46e971d11a6b58c2 (diff)
downloadcpython-68e85e583484d1fde2170ea768413eae818aa050.zip
cpython-68e85e583484d1fde2170ea768413eae818aa050.tar.gz
cpython-68e85e583484d1fde2170ea768413eae818aa050.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 implementation 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.
Diffstat (limited to 'Lib/test/test_optparse.py')
0 files changed, 0 insertions, 0 deletions